Slash commands

Slash commands drive chat without typing prose — and they're a Refine-tier capability. On Refine, type / in any chat to see the picker; pick a command or keep typing to filter. On Discover and Build you chat in plain language — ask about your notes and constellations — and the command picker doesn't appear; the change-making commands live at Refine.

Commands either operate on the chat's referenced notes (so you need at least one reference) or stand on their own.

Ten commands ship, all at the Refine tier.

How a command runs

A command doesn't run as soon as you send it. Bridge first shows a confirm card with the command, its targets and the options it understood.

• A missing text input gets a text field. /note on its own asks "What should the note say?"
• A missing choice gets chips, for example which expansions /expand should run.
• Missing @ targets get a sentence saying which targets the command needs, such as "Needs two @ targets: a note, then a note or constellation." Edit puts the command back in the message box so you can add them.
• Too many targets: /connect and /disconnect take exactly two. Give them more and the card says "Takes exactly two @ targets: a note, then a note or constellation."

Run turns on only when everything is filled. Cancel closes the card without running anything.

A failed command's reply shows as an error, with a rust border and an error icon, so it can't be mistaken for a normal reply.

Targets: @

Commands take their targets from @ mentions. @ reaches the chat's notes and constellations, any other constellation, and any plan. A target outside the chat is marked This message only and applies to that message; the chat's references don't change.

A command that works on notes uses the chat's notes when you give it no @ targets. /expand, /connect and /disconnect never do: they act only on the targets you name.

You can type a target instead of picking it, as in /replan @[Marathon plan] or /connect @[Pricing idea] to @c4. See Chat for how a typed @ links.

/expand

Queue a deeper research pass on the notes you @-pick.

Usage: /expand @[note] idea feature. It takes @ targets: notes, or a constellation for all its members. It never falls back to the chat's notes.

It queues the notes through the same path as a note's Expand, and the card's chips choose which expansions run. Bridge replies at once with what it queued and what it didn't, and why: a Reference note, a note that isn't classified yet, a note that's already being expanded, or the daily limit of 50 expansions. Results arrive in your Inbox (idea, feature, product) or on the note (general). A failed run says why in the chat, with AI & Models settings and Retry, and a failed idea, feature or product run also leaves an Inbox item.

Use it when an Expandable note is starting to feel important and you want more of the AI's thinking on it before deciding whether to start a venture.

/plan

Generate a portable plan document set for this chat.

Requires references: yes.

Triggers a Build Plan run against the chat's referenced notes. Equivalent to tapping the Start a venture button, but from inside the chat surface. The generated plan lands in the Plan tab and a link appears in the chat.

/findings

Show cross-project connections and contradictions for the referenced notes.

Requires references: yes.

Runs a direct query over your connected notes — surfacing contradictions, cross-project links, and supporting/elaborating connections on demand, rather than waiting for a background pass. If nothing has surfaced for those notes yet, it tells you so.

/summarize

Summarize the referenced notes into a paragraph.

Requires references: yes.

A one-paragraph plain-prose summary of the referenced notes. Useful when you want to copy-paste a quick brief out of Bridge — for an email, a Slack message, a kickoff doc.

/note

Draft a new note. Approve it in chat before it persists.

Requires references: no.

Drafts a new note from the text you give, for example /note bookmark the pricing idea. The draft appears in the chat as an unsaved note card with an Approve / Reject control. Approving it persists the note to your Notes tab and adds it to the chat's notes; the chat says "Saved drafted note. Added to chat references." Rejecting it discards the draft. Useful when a chat surfaces an idea worth capturing as its own first-class note.

/connect

Connect a note to another note, or add it to a constellation.

Usage: /connect @[note] to @[note or constellation]. Needs two explicit @ targets: a note, then a note or a constellation.

It does what a note's Connect sheet does: the same graph check, your similarity cutoff, and the same Connection added Inbox item. A note that isn't in the graph yet joins a constellation through one of its notes, which /connect can't name, so Bridge asks you to use the note's Connect sheet instead.

A Reference note isn't part of the graph, so it can't be connected to a note or a constellation. Bridge says so as an error and changes nothing, for example: "Reading list" is a Reference note. Reference notes aren't part of the graph, so they can't be connected. A note's Connect sheet says the same.

Adding a note the chat picked to a constellation the chat references moves it under that constellation in the chat's count. A note you add to a constellation by hand stays in that group through Apply changes (see Constellations).

/disconnect

Remove a connection between two notes, or remove a note from a constellation.

Usage: /disconnect @[note] from @[note or constellation]. Needs two explicit @ targets: a note, then a note or a constellation.

• Note from note removes both your connection and Bridge's automatic one between the two notes. Neither note leaves any constellation. With nothing to remove, Bridge says No connection between "A" and "B" to remove.
• Note from constellation takes the note out of the group the same way leaving does (see Constellations). The reply says how many connections it cut, and That ended "…". when the group had too few notes left to stay a group.

While Bridge is regrouping your graph, both say Regrouping your graph — try again in a minute.

/replan

Regenerate a plan in place from its source notes.

Usage: /replan @[plan].

Regenerates the plan from its current source notes, keeping the same plan. The plan doesn't have to be in the chat. You're notified when it's ready.

/editplan

Draft an edit to one of a plan's files.

Usage: /editplan @[plan] <instruction>, for example /editplan @[plan] make the timeline more aggressive.

Drafts an edit to one plan file, which you approve before it's applied. See Refining a plan for the approval flow.

/help

List the available slash commands.

Requires references: no.

Prints the command list with one-line descriptions. Run it inside a chat as a reminder; the picker also shows the list as you type /.

Errors

Each command surfaces one of these states in the chat:

• Unknown command — you typed /somethingelse. Bridge replies: "Unknown command: /somethingelse. Try /help."
• Missing references — you ran /plan, /findings or /summarize without any notes in scope. Bridge replies, for example: "/summarize needs at least one referenced note. Tap the + in the chat header to add one."
• Missing targets — the confirm card says which @ targets the command needs.
• Tier-gated — you ran a command below the plan it needs. Bridge replies "/expand requires the Refine plan.", with a See plans button that opens the Plan page.
• Command failed — the reply shows as an error. A failure from your AI provider shows the provider's reason, for example "Your OpenAI key is out of credit. Add credit with OpenAI or switch model in Settings.", with AI & Models settings and Retry. Any other failure reads "/<command> failed. Try again."

Tier gating

Slash commands are a Refine-tier capability. Discover and Build chat in plain language — they can ask about their notes and constellations, but can't drive changes through commands. Refine and Refine LTD include all ten commands.

Adding new commands

Bridge ships with ten. We can add new commands without an architectural lift — they show up in the picker and /help output automatically when they ship.

Next

• See Chat for the chat fundamentals (note vs constellation vs plan scoping).
• See Refining a plan for how /plan and /expand combine with the Refine-tier diff-approval flow.
• See Tier comparison — slash commands enter at Refine.