Bridge documentation
Welcome. This wiki is the canonical reference for everything visible to you inside the Bridge app — how notes work, what constellations are, what the Build Plan produces, every slash command, the full tier breakdown.
If you've used Bridge before, jump straight to what you need. If this is your first visit, start with the Getting Started section.
Quick paths
- First time? → What Bridge is → Quick start
- Want a worked example? → Your first venture
- Looking for something specific? → Press ⌘K (or Ctrl-K) to search.
Sections
Getting Started — the product overview, an install + first-note walkthrough, and a full idea-to-plan worked example.
Core Concepts — Notes, Constellations, the Graph view, Build Plan, and Chat. The five primitives the rest of the wiki references.
Guides — opinionated how-tos: capture habits, refining a plan with the Refine-tier diff approval flow, sharing a plan with your team or your terminal, and how Bridge handles ambiguity when it generates a plan.
Reference — the full tier matrix, the eight Build Plan output files with size budgets, the six slash commands, and the FAQ.
What Bridge does
Bridge is a mobile-first planning tool for software developers and builders. You capture raw ideas on your phone — voice memos, bullet notes, half-formed thoughts — and Bridge turns them into implementation-ready specifications: database schemas, API contracts, component trees, and a full plan document any coding agent can work from.
The workflow has four stages. Capture is zero-friction: write, dictate, or paste anything into the Notes tab without worrying about format. Explore is automatic: Bridge runs a semantic pass over your notes, groups related ones into constellations, and surfaces them as candidate projects. Specify is one tap: pick a constellation, start a venture, and receive a complete spec set. Refine is conversational: open a chat scoped to specific notes or a generated plan and drive changes with plain language or slash commands.
Bridge is BYOAPI — you supply your own Anthropic, Gemini, or OpenAI API key. Your subscription pays for access to the workspace and the planning engine, not for AI inference. Charges for AI calls go directly to your provider account at their standard rates.
How to use these docs
The docs are organized around the four stages above. Core Concepts explains each building block (notes, constellations, the graph, Build Plan, Chat) in detail. Guides give opinionated walkthroughs for real-world tasks: building a capture habit, refining a generated plan through the diff approval flow, sharing a plan with a developer or piping it to a terminal. Reference is the exhaustive lookup section — the complete tier matrix, every Build Plan output file with size budgets, every slash command, and the FAQ.
A note on what's in the docs
These docs describe what's visible to you in the app — the buttons you tap, the files Bridge produces, the commands you can run. They don't describe Bridge's internal architecture or implementation details.