We’re live on Product Hunt.
You don’t have to run the coding agent to shape what it builds. Review its plan in your browser, answer its open questions, and approve the version it builds.
https://t.co/tqwg7SMNPF
The person who knows what should happen for customers may not be the person running the coding agent.
Pathmode gives them a place to review the proposal, correct it, and approve the version the agent builds from.
https://t.co/cSvzV9cWd9
Really liked @jboogie’s piece on turning a product hypothesis into an AI eval before building. Write down what would prove you wrong, test on real inputs, agree on the passing bar upfront.
A few things we learned the hard way building Pathmode’s intent checks:
• Check the grader. Ours agreed with the bad answer it was meant to catch, 2 runs out of 2.
• Run the known-bad version too. One eval passed both the fixed and the broken prompt, 36 of 36 each. It couldn’t see the bug.
• Keep some cases out of sight. A perfect score means nothing when the cases resemble examples already in your prompt.
And passing the eval is still just a reason to try it with users. You still have to find out whether it helps.
https://t.co/lJ0XXNDFZC
An agent can implement today’s request correctly and still undo something your team learned months ago.
We’re building Pathmode to carry those decisions and the evidence behind them into the next build.
@creedants Fixed in Pathmode MCP server 1.35.5 (plugin 0.1.41). Without an API key, some tools read the intent file from wherever the server was started, not the repo your editor has open, so a new checkout kept the old spec. Pin 1.35.5 in your MCP config, restart once, and let us know.
Cleaned up https://t.co/7kZNKNiX25.
Check an intent.md → CLI
Draft specs in Claude Code → plugin
Cursor/Codex/Desktop → MCP server
Validate in CI → Action
Implement the format → IntentSpec
Start here: https://t.co/7kZNKNiX25
@creedants Could you check which plugin version you’re running? We’ve shipped quite a few updates recently. Try updating to the latest version and restarting the MCP server, then let us know if you still get the old IntentSpec.
“Build a duck.”
✅ Is duck
✅ Stands up
✅ No parts left over
“It was supposed to be a pirate.”
New ticket: make duck eligible for maritime crime.
This is why we're building Pathmode. Settle the missing decision before the build. https://t.co/SmzlmGbokG
Before handing an intent.md to a coding agent, what decisions are you leaving it to guess?
I ran Pathmode’s preflight on a worked example following the structure of Anthropic’s AI-native SDLC playbook.
The original spec said:
“Customers see shipment status and the expected delivery date in their account.”
But what should happen when the shipment API is down? Preflight flagged the missing failure behavior. The revised spec adds:
“The shipment API is down: the page shows the last known status and when it was checked.”
That’s one less product decision left for the coding agent to guess. The check also flagged gaps in outcomes and verification. The additions kept the author’s context and open questions intact.
Try it against your existing file:
npx @pathmode/cli preflight
It finds files under intent/<feature>/intent.md too. Free, local, no account.
Worked example with the before-and-after specs and verdicts:
https://t.co/faZNfKNLeA
@realSamHu Yes! We also keep what the agent proposed separate from what the team authorized. The next session needs the decision and its reasoning, including which alternatives were ruled out.
“Add a cancel button” leaves a product decision unanswered: Does access end immediately, or when the paid period ends?
Pathmode brings that choice back to your team, and carries the answer into the coding agent’s next session.
The agent proposes. You decide.
We’re evaluating Jev from @TypeSafeAI for evidence classification in @pathmodeio: turning customer feedback into labels like friction, observation, or feature request while preserving the original words.
Curious how its speed and confidence estimates hold up on messy feedback.
“Let customers export their table.”The agent proposes exporting the current page. You meant every filtered result.That’s a product decision worth catching before implementation.https://t.co/wJNpYHMwxl
New in Pathmode: Your coding agent has a plan. Does it reflect what you meant?
We are building Pathmode so product owners can review the proposal, resolve missing decisions, and approve what gets built.
The agent proposes. You decide. Findings come back to you.
Product decisions and coding agent setup often belong to different people.
We rebuilt Pathmode for that handoff: invite the teammate running the agent, start the brief while they connect, and follow it to a verified repository connection.
An invite isn’t a connection.
https://t.co/zEcmk0OXor
@itzSaasified Someone still has to decide which problem matters, what tradeoffs are acceptable, and what evidence would prove the solution worked.
Intent engineering is new software engineering.
Google’s new whitepaper on vibe coding makes a strong case: as AI accelerates implementation, specification, verification, and human judgment become more important.
That’s the part I keep coming back to: judgment.
We’re getting better at telling agents how to work. Repository instructions, tools, guardrails, tests, evals.
But there’s another set of questions:
Why is this the right problem to solve?
Which customer evidence supports it?
What tradeoff did we make?
Who approved the direction?
What would make us reconsider?
A test can verify that a payment retry works. It can’t establish that payment retries were the reason customers abandoned checkout.
You can pass every check and still build the wrong thing.
The paper argues that intent is becoming the interface for software development. I agree. But intent needs to carry more than a description of the desired implementation.
It needs the reasoning behind the work—and a way to change that reasoning when implementation or customer behavior reveals something new.
That’s what we’re building with Pathmode: a connected record from evidence to intent, through implementation, and back to outcomes.
Our starting point is simple: an intent.md alongside your code. What problem you’re solving, why it matters, what success looks like, and the boundaries an agent must respect.
The bigger opportunity is keeping that intent alive: recording decisions, bringing implementation findings back into refinement, and checking whether what shipped actually helped.
Faster coding makes it cheaper to build an idea.
We still need to know which ideas deserve to become software.
https://t.co/F8vNjfoWf7