Bridge

Sharing a plan

Once you've generated a Build Plan, you need to get the files out of Bridge and into the project where your coding agent will read them. Bridge supports three paths.

Download as zip

The most common path. From the Plan tab, tap the plan artifact, then tap Download zip.

You get a zip containing the eight plan files at the top level plus the AGENTS.md overlay:

my-plan.zip
├── 00_index.md
├── 01_brief.md
├── 02_user_flow.md
├── 03_architecture.md
├── 04_data_model.md
├── 05_tasks.md
├── 06_acceptance.md
├── 07_scope.md
└── AGENTS.md

Unzip into your project directory. The AGENTS.md file goes at the project root; the eight numbered files can sit at the root or in a plan/ subdirectory — whatever fits your project layout. Update the AGENTS.md overlay paths if you move them.

Share via system share sheet

On mobile, the Plan tab supports the OS share sheet. Tap Share, pick a destination (AirDrop, Files, email, your favorite cloud drive). The zip flows wherever your share sheet can send it.

This is the right path when:

  • You want to AirDrop the plan to your laptop without going through cloud storage.
  • You want to email it to a teammate.
  • You want to drop it into Files for a specific project folder.

Pipe to your terminal (post-launch)

If you live in the terminal, the future path will be a shareable link the Bridge CLI plugin can fetch directly. That CLI plugin is V2 work — it ships post-launch.

Until then: use the zip download path and unzip into your project root.

How the AGENTS.md overlay works

AGENTS.md is the file your coding agent reads first when you start a session in the project directory. It tells the agent:

  1. This project is planned by Bridge.
  2. Read the eight plan files in this order.
  3. Follow a small working agreement about how to execute tasks and update 05_tasks.md as work progresses.

You don't have to write AGENTS.md — Bridge generates it as part of every Build Plan. You just need to make sure it sits at the project root where your coding agent will find it.

What to do once the plan is in your project

  1. Open your project in your coding agent of choice.
  2. The agent reads AGENTS.md automatically (or you point it at the file).
  3. The agent works through 05_tasks.md in order, updating task status as it goes.
  4. After each task, the agent verifies the task's accept-when condition before moving on.

When you come back and re-open the session, you can read 05_tasks.md to see the agent's progress. Tasks marked Status: done are complete; tasks marked Status: pending are still ahead.

When to regenerate vs ship

If you discover the plan is off, two options:

  • Small change — open the chat scoped to the plan and use the Refine-tier diff approval flow (Refine tier only). See Refining a plan.
  • Big change — add more notes to the source constellation, regenerate the Build Plan, and download the new version. Old versions stay in the Plan tab archive.

Sharing with a teammate

Bridge plans are markdown — they read in any text viewer. You can:

  • Drop the zip in shared cloud storage and let your teammate unzip it.
  • Email it.
  • Commit the plan files to your project's repo. They're meant to live alongside your code.

When the plan is in shared cloud storage or a repo, your teammate doesn't need a Bridge account to read it. Bridge accounts are only required to generate and refine plans.

Next

← Back to DocsPre-order Bridge