About Pathmode
Your team should shape what AI builds.
Pathmode helps product, design, and engineering review what coding agents propose, agree on what should happen, and carry those decisions into future work.
Janne Lammi
Founder · Finland
A note from the founder
Why I’m building Pathmode
I started Pathmode as a workspace where product teams wrote specs for coding agents. Usage showed me something different: the agents were already writing the specs. People needed a way to decide whether to stand behind what the agent proposed.
That is what Pathmode is built around now. Engineering brings the reality of the code; product and design bring the intended behavior. The decision and its reason need to survive that conversation, so the next request can use them.
Before Pathmode, I built Patternry, a design-systems and UI-pattern library, under a different company. I founded Pathmode Oy in 2026, in Finland, to help teams carry their product judgment into what AI builds.
When you write to Pathmode about a bug, a question, or a workflow you want to try, you’re writing to me, the person building it.
Our commitments
What we build around
People own the decision.
Agents can propose a plan and check the code. The people responsible for the product decide what should happen and approve the exact revision to build. Automated findings remain advisory.
The reasoning should last.
A decision needs its reason. We keep the evidence, tradeoffs, and findings available so the next request can build on what the team learned, or revisit it when things change.
Your intent stays yours.
The agreed intent.md lives beside your code in the open IntentSpec format. Our local tools work without an account. Your repository keeps the decision even if you stop using Pathmode.
One decision, in practice
A Cancel plan button hides a product decision.
The request says “add a Cancel plan button.” It doesn’t say when access should end. That is a decision the team needs to make before the agent builds.
1. The agent proposes
End access immediately when a customer cancels their plan.
2. The team corrects
Keep access until the paid period ends. The customer has already paid for that time.
3. A person approves the revision
The agent revises the proposal. The responsible reviewer checks it and approves that exact revision before implementation.
The approved intent stays beside the code. The workspace keeps the reason available when a later request touches cancellation. New work still needs its own review and approval.
Follow the complete reviewCompany at a glance
- Company
- Pathmode Oy
- Founded
- 2026
- Based in
- Finland
- Founder
- Janne Lammi
- Open standard
- IntentSpec
- Contact
- hello@pathmode.io
A few practical questions
Is Pathmode the same company as Patternry?
No. Patternry was an earlier product by Pathmode’s founder, Janne Lammi, under a different company. Pathmode Oy is a new company, founded in 2026.
Do I need a Pathmode account to use intent.md?
No. intent.md follows the open IntentSpec standard. The local MCP server and CLI work without an account or API key. A connected workspace adds team review, approval, private evidence, and decision history.
What happens to my work if Pathmode stops?
Your authorized decisions stay in your repositories as intent.md files in the open IntentSpec format. The MCP server, CLI, and IntentSpec are MIT-licensed, and the local tools run without Pathmode’s servers. Review history and private evidence live in the connected workspace; you can request a complete machine-readable export at any time.
For setup and plans, see the developer tools and pricing.
A direct conversation
Tell me what your team is working through.
A question, a bug, or a workflow you want to try. Your email comes straight to me.