Humans should review ideas, not code.

Pathfinder is a shared product engineering workspace for you, your team, and your coding agents. Plan and review your product's features, design, and architecture.

Pathfinder showing the Pick up where you left off mission for Phanpy, open on its first stage, Understand

The example project, Phanpy, is open source under the MIT licence, by Lim Chee Aun. Its name and logo are his; Pathfinder is not affiliated with it.

Review the ideas that shape your product.

You can't guide what you can't see. Pathfinder shows your product's building blocks: its components, its words, and its architecture. You and your agent share one picture, so you can steer every choice toward quality.

  1. Discover the right problem

    Review the evidence, not a hunch. You and your agent work through your customers' problem. Then you decide its priority and requirements before anyone designs a thing.

  2. Choose the right solution

    Review working prototypes, not pull requests. Your agent builds several from your own components. You pick the one that feels right, and polish it together.

  3. Shape the right architecture

    Review a diagram, not a diff. Your agent draws the change, and you decide its modules and interfaces before any code is written. The diagram stays current with your code.

  4. Use the right words

    Review a glossary, not every name in your code. You and your agent give each idea one name, so your app, code, and docs say the same thing.

  5. Set the right style

    Review your design system, not your stylesheets. You choose your colours, type, grid, shapes, and motion, and your agent keeps every prototype and feature on brand.

  6. Build from the right components

    Review screenshots, not markup. You and your agent polish every component in your app, so each new feature starts from parts you trust.

  7. Follow the right practices

    Review a checklist, not every config file. See which product and engineering practices your project is missing, and choose the gaps to close. Each one gives your agent better feedback, on every mission and quick fix.

  8. Run the right steps

    Review a runbook, not every command your agent types. You and your agent write down how your project is run, tested, and released, with a check for each step and the traps to watch for. Your agent records each run, so you see which runbooks still work.

The Understand stage of the Pick up where you left off mission: the problem statement and the current state, beside the Prioritise stage

Augmented product engineering.

Work together with your agents to build products that feel crafted, not generated.

Keep your setup.

Pathfinder works alongside the agent you already use.

Connect your agent, and it will map your existing codebase into Pathfinder, or help you start a new product.

Get started in Claude Code$ claude mcp add --transport http pathfinder https://api.pathfinder.com.ai/mcp

Using another agent? Add this address as an MCP server: https://api.pathfinder.com.ai/mcp

Antigravity
Claude
Claude Code
Codex
Conductor
Cursor
Herdr
Hermes Agent
Orca
Paradev
Pi
T3 Code
Visual Studio Code
Zed

Find your product's path.

Build the product you've dreamed of, at the quality your customers deserve.

Pathfinder example project