The trail map for AI coding agents

You pick the destination. Your agents walk the trail.

Big work is a long trail, and agents get lost on long trails. Scout keeps the whole party on one map, together, and only calls you back for the turns that are yours to make.

Start at the trailhead npx teamtrail
See the route
Why Teamtrail

Big work gets lost in one chat.

One agent in one chat can manage a short walk. A real project is a long trail: dozens of decisions, several agents and you, over days.

  • 01

    The trail goes cold

    Every new session starts from zero. What was tried, what was decided and why gets left behind between chats.

  • 02

    Agents stop at a fork, silently

    An agent needs a call from you and stops. You find out an hour later, in a terminal you weren't watching.

  • 03

    Nobody knows how far you got

    Agents say “done”. Without checks and a record, you walk the whole route again before you can trust it.

The party

A trail, a party, and a scout who keeps them together.

Every part of the work has a clear owner, so you steer the journey instead of herding chats.

The trail

Big work, mapped as decisions

Describe an idea and it becomes a map of tickets: what to research, what to decide, what to build, and what blocks what.

The guides

Your agents, each on the right stretch

Claude Code, Codex or any agent that speaks MCP picks up whatever is unblocked. A second agent reviews the work.

Scout

The guide who keeps everyone on the path

Scout hands out work, keeps each agent up to date, records every decision, and tells you what happened when you get back.

You, the trail lead

Only the turns that need you

Questions from every agent land in one inbox with suggested answers. Decide, and the party moves on.

How a trail runs

From trailhead to destination.

Five stages, on one map that runs next to your code.

The New trail form with title, destination, notes and mode.
01

Mark the destination

Say what you want to build and what done looks like. Start it in the Lookout or in your agent's chat. Scout asks a few questions, then draws the route.

  • Questions, decisions and building in one map
  • Plan only, or plan and build
  • Kept in your repo, or in GitHub Issues and Linear
A discovery brief waiting for review: what exists, the product rules that apply, risks and assumptions.
02

Learn the terrain first

Before anyone sets off, an agent looks at what you already have and writes a short brief: what exists, what could break and what it's assuming. You approve it, or ask for changes.

  • Nothing gets built until you approve the brief
  • Your product's rules and users, not just the code
  • What it learns is kept for every task after
The trail map with the first tickets charted and agents working on them.
03

The party sets off

Agents pick up the work that's ready and walk side by side. Each one carries what your project already knows, so you never explain the same thing twice.

  • Each agent can work in its own copy of your project
  • If an agent goes quiet, its work goes back in line
  • When the ground changes, they propose a reroute for you to approve
An agent's draft resolution waiting for the trail lead, with suggested replies.
04

You call the junctions

Everything that needs you waits in one list, most important first, with suggested answers. Reply in a click, or from your agent's chat with /scout inbox.

  • Only urgent questions interrupt you
  • You decide which calls are always yours
  • Small ones are made and written down for you to review
A decision record with the answer, the alternatives considered, the rationale and the transcript.
05

Arrive with proof

You agree on what done means before anyone sets off. Every point needs proof: your tests, a second agent's review, or your sign-off. Every decision goes in the logbook, with the reasoning.

  • Your product's rules become points to prove
  • Claude and Codex review each other's work
  • A trip report: time, your input, rework and cost
What makes it different

Built for trails that take weeks.

Your agents can already write the code. Teamtrail is what lets you send them on the long route and still sleep at night.

01 · Plans that adapt

Reroute when the ground changes

Agents write down what they assume. When something turns out wrong, they propose a new route, and they'll even tell you when you're climbing the wrong mountain. Nothing changes until you say yes.

02 · Your attention

Only the turns that need you, in order

Every question, approval and stuck task in one list, most important first, with the reason it matters. Only urgent calls interrupt, and you decide which calls are always yours.

03 · Proof

Arrived means proven, not claimed

Agree on what done means before anyone sets off. Every point needs proof: your tests, your sign-off or a second agent. Claude and Codex check each other's work.

04 · A real party

Many agents, nobody lost

Each agent works in its own copy of your project, and Scout warns you before two of them touch the same files. You review every branch; nothing is merged for you.

See every feature
What it isn't

Not another agent orchestrator.

Orchestrators help agents do more work. Teamtrail helps you trust more work with less of your attention.

Not for quick fixes

A short walk doesn't need a map

A five-minute change? Just ask your agent. Teamtrail is for work that runs for days, across many agents.

Not autopilot

The big turns stay yours

Agents handle the small decisions and write each one down, so you can check or change it. Anything that matters comes to you.

Not a runner

It never starts agents on your machine

Your agents run where they always do, in your terminal. Agents that keep walking with your laptop closed are what Cloud is for.

Not a feed

No play-by-play of every step

You see what needs you, in order, and why. The rest is in the logbook when you want it.

Guides Coming

Bring a guide for the hard stretches.

Every trail has its own terrain. Add a security reviewer, a QA lead or a docs writer to your party, and any agent that picks up their tickets works to their checklist.

Meet the guides
  • ReviewerChecks the change against what was claimed
  • QATests the edges before it ships
  • SecurityLooks for what an attacker would
  • DocsKeeps the docs true to the code
  • ArchitectGuards the shape of the system
  • + Your ownWrite a role for your team
Yours to run

Your map, on your machine, with your agents.

  • Local-first

    Teamtrail runs on your computer. There is no Teamtrail server and no account.

  • Plain files

    Trails and decisions are markdown in your repo, or issues in GitHub or Linear.

  • Any agent

    Claude Code and Codex today, and any agent that connects over MCP.

  • Evidence over claims

    Checks run in your repo and every verdict is kept, so “done” means done.

Questions

Questions, answered.

What is Teamtrail?
A trail map for planning and finishing big projects with AI coding agents. It runs on your computer and shows every trail, ticket, agent and open question in one window.
Who is Scout?
Scout is your guide in the Lookout. It hands out work, relays agents' questions to you and tells you where the trail stands. It never answers on your behalf.
Which agents does it work with?
Any AI coding agent that connects through MCP. Claude Code and Codex have first-class support: one command connects them and adds the /scout command to their chat.
Can I stay in my agent's chat?
Yes. /scout new turns an idea into a trail, /scout resume picks up the work, /scout status tells you where things stand, and /scout inbox lets you answer waiting questions in the chat. The Lookout shows it all live.
Does my data leave my machine?
Teamtrail keeps your plans in your project folder. If you connect GitHub or Linear, your computer talks to them directly and your keys stay on your computer. Your agents still use their own AI services.
Can I set it up without the Lookout?
Yes. Everything Teamtrail reads is a plain file in your repo or a command in your terminal: checks, what's always yours, interruptions, workspaces and trackers. The docs cover every setting, with examples.
Can an agent make a decision for me?
Only small, everyday ones, and each is written down so you can review it or change your mind. You decide what always comes to you: by default, anything that changes your data, security, billing or your public API.
Does Teamtrail run my agents for me?
Not on your machine. You start Claude Code or Codex as usual, and they connect to Teamtrail. If you want agents that keep working in the background while you're away, that's Teamtrail Cloud, coming soon.
Can several agents work at the same time?
Yes. Each one can get its own copy of your project on its own branch, and you hear about it before two agents change the same files. If they do, Teamtrail suggests a ticket to bring the work together. It never merges anything for you.
What if the route turns out to be wrong?
An agent that finds a wrong assumption proposes a reroute, with the evidence and a before-and-after on the map. The work it affects pauses, and nothing changes until you approve. If the work already exists or the trail is on the wrong mountain, an agent can say so and suggest a better goal.
Does it understand my project?
Yes, and it keeps learning. Before building, an agent studies your code and asks about your product, then writes a brief you approve. What agents learn along the way is saved, so the next task starts where the last one left off.
How do I know the work is really done?
Before an agent starts, it writes down what has to be true, and you can confirm it. When it finishes, every point needs proof from your tests, a review by another agent, or your own sign-off. Anything without proof goes back.
Is it free?
Yes. Teamtrail is free to use and runs on your computer.
How do I install it?
Run npx teamtrail in your project folder (Node.js 20 or newer). Then connect your agent with npx teamtrail connect claude or npx teamtrail connect codex. Pick Demo in setup to look around a ready-made trail first.

Ready to hit the trail?

One command in your project folder. The Lookout opens in your browser and Scout walks you through the rest.

Start at the trailhead npx teamtrail