Usage
PlanBridge opens a local browser UI where you annotate markdown and the result flows back to your agent. There are three ways to get content into that UI.
Plan-mode collaboration
Section titled “Plan-mode collaboration”Your agent calls contextbridge through its standard plugin or hook system when it finishes a plan, and PlanBridge opens automatically. You annotate, then approve or send it back. The install script adds those entries for any supported harness it detects.
Precision feedback on a file
Section titled “Precision feedback on a file”Ask your agent to open an existing markdown file on demand: /planbridge-open <path> in Claude Code or $planbridge-open <path> in Codex CLI. Good for a design doc, RFC, or spec that never went through plan mode.
See Precision feedback on a file.
Annotate the last message
Section titled “Annotate the last message”Mark up the long answer your agent just wrote: /planbridge-last in Claude Code or $planbridge-last in Codex CLI.
See Annotate the last message.
Supported harnesses
Section titled “Supported harnesses”| Harness | Status | Docs |
|---|---|---|
| Claude Code | Supported | Hook on PermissionRequest:ExitPlanMode |
| Codex CLI | Supported | Hook on Stop |
Other agents
Section titled “Other agents”Any agent that can run shell commands and parse JSON can use PlanBridge directly. You instruct it to pipe its plan to contextbridge plan and read the response on stdout. See Other agents for the prompt to give your agent and the response shape it should expect. Cursor, Aider, opencode, Gemini CLI, and Aether all fit this pattern.