Chat
Bridge's chat is intentionally different from a generic chat-with-an-LLM tool. Every conversation has an explicit reference set — specific notes, a constellation, or a plan — and the AI answers using only those references.
Why scoping matters
When you chat with a general AI assistant, you have to either (a) paste your context in every turn or (b) trust the AI not to drift. Both are unreliable. Bridge fixes this by making the reference set a first-class part of the chat: you pick what's in scope, the AI never goes outside it, and you can swap the references mid-conversation without losing the thread.
Three scope types
Note references (Free and above)
Pick one or more individual notes. The AI sees those notes' raw text and expansion (if available). Useful for asking the AI to summarize a few related notes, or to surface contradictions across them.
Constellation references (Discover and above)
Pick a whole constellation. The AI sees every note in the cluster plus the constellation's AI-generated name and theme. Useful for "what's the through-line in this cluster" or "what's missing from this body of thinking" questions.
Plan references (Build and above)
Pick a generated Build Plan. The AI sees all eight plan files plus the AGENTS.md overlay. Useful for "explain this plan to me" or "what's the riskiest part of this plan" questions.
Refine-tier: chat that writes
On the Refine tier, chat can do more than read — it can propose edits to plan files when a plan is in the reference set. The flow:
- You ask the AI to change something ("simplify the data model" / "add an authentication step to the user flow").
- The AI proposes the change as an inline diff in the chat.
- You approve or reject each diff.
- Approved diffs write through to the plan files immediately.
You stay in control — nothing changes in your plan without your explicit approval per diff. Rejected diffs disappear; you can ask the AI to try again with different guidance.
Modifying references mid-conversation
You can swap which notes/constellation/plan the chat references at any point in the conversation without losing the thread. Tap the + in the chat header to add a reference; tap an existing chip to remove it.
This is useful when a chat that started about one cluster of notes leads to a tangent in a different cluster. Instead of starting a new chat, add the new reference and keep going.
Slash commands
Slash commands are a Refine-tier capability — on Refine, drive chat with the six commands that ship in the MVP:
/expand— deeper research pass on referenced notes/plan— generate a Build Plan for the referenced notes/findings— show cross-project connections and contradictions/summarize— summarize the referenced notes/note— draft a new note (you approve before it persists)/help— list available commands
See Slash commands for the full reference.
Tier gating
| Capability | Free | Discover | Build | Refine | |---|:---:|:---:|:---:|:---:| | Chat with your notes (ask-only) | ✓¹ | ✓ | ✓ | ✓ | | Reference a whole constellation | — | ✓ | ✓ | ✓ | | Reference a generated plan | — | — | ✓ | ✓ | | One active chat (delete to start another) | ✓ | ✓ | ✓ | — | | Unlimited chats | — | — | — | ✓ | | Slash commands | — | — | — | ✓ | | Chat proposes plan edits (write) | — | — | — | ✓ |
¹ Free can open one chat once you've added your own API key.
Next
- See Slash commands for the full command reference.
- See Refining a plan for the Refine-tier diff-approval workflow.
- See Tier comparison.