Bridge Layer
bridge CLI form, so this district, the API Reference CLI catalog, and the Infrastructure service map teach one command vocabulary. The same contract names the bridge request-envelope source (bridgeHeaders and extraHeaders in packages/bridge): the wrapper contract below names the authenticated envelope every request carries.Choose the shortest Bridge exit first. The deeper layer split below only matters when the first stop still is not obvious.
- Verified wrapper surface: Atlas teaches call, watch, result, interject, cancel, and list as the first-class Bridge v1 verbs, with the call-versus-detach choice explicit; legacy aliases remain only for compatibility, and every request carries the bearer-wins envelope — per-target headers, then the env layer, Authorization set last.
- District boundary: This landing stays the quick sorter between wrapper rules, the deeper transport semantics, and the coordination lane that decides who should receive the request.
- Follow-on routes: Bridge Communication still owns the transport model and Coordination Patterns still owns the multi-agent workflow context after the owner is already clear.
Choose the bridge question you arrived with first
Open the street page when you need the transport model itself: call, watch, result, interject, cancel, and list semantics plus the shortest explanation of when a turn waits, detaches, or stops.
Keep these three layers separate
Use this page for the short answer about wrapper verbs, route split, and where to go next.
It is the sorter, not the full protocol reference.
Open the street page when you need call, watch, result, CLI defaults, or the path chooser in more depth.
This is the teaching page for transport semantics.
Open the coordination street when the transport is only one step inside a longer owner-selection or handoff loop.
This is where Bridge joins the broader workflow story.
Keep the verb-first wrapper above the deeper transport docs
Use call when the caller needs a bounded answer now. The command creates the turn and waits for its result unless you explicitly detach it.
bridge call atticus "Proposal: add search to Atlas. Approve?" --jsonChoose call when you need a bounded answer now; add --detach when the work should continue independently. Then watch its events or read the result snapshot by turn ID.
bridge call scout "Audit the Bridge docs and report one concrete drift." --json
bridge call scout "Audit the Bridge docs and report one concrete drift." --detach --json
bridge watch <turnId> --resume --json
bridge result <turnId> --jsonUse interject when an existing session needs a focused follow-up without starting a duplicate turn.
bridge interject <sessionKey> "Focus on the service-directory examples." --jsonUse cancel when a queued or running turn is stale, superseded, or no longer safe to continue.
bridge cancel <turnId> --reason "stale" --jsonUse list to inspect the bounded local Bridge turn history when you need to recover a turn ID or session key.
bridge list --jsonEvery Bridge request — call, watch, result, interject, cancel, or list — carries an authenticated envelope: the target’s configured headers first, then the BRIDGE_EXTRA_HEADERS env layer, with the Authorization bearer set last so the target token always wins. A malformed env value fails closed instead of sending a partial envelope. The /bridge route teaches the full envelope contract.
target headers → BRIDGE_EXTRA_HEADERS (env) → Authorization: Bearer <target token> (set last, always wins)Use recurring handoff paths as examples, not live status
Governance or policy approval is required before a new route or major concept lands.
Design direction or a post-ship UI audit is needed on an existing Atlas surface.
Atlas wants a bounded freshness or historical-context pass before choosing the cycle slice.
Code review or implementation work belongs with Currybot rather than Clawdy itself.