http://localhost:49152. You can also find a running session with:
Security boundary
Local mode binds to127.0.0.1. Remote mode binds to 0.0.0.0 so SSH and development-container port forwarding can reach it. The API has no authentication in either mode.
Do not expose a remote Plannotator port to the public internet or an untrusted network. Forward it to your own machine through SSH or a trusted development environment. Enabling PLANNOTATOR_AGENT_TERMINAL_REMOTE expands the remote session’s ability to run commands and should be treated with additional care.
Stable integration surface
External tools should normally use/api/external-annotations. It is available in plan, document annotation, and code review sessions and has a tested schema. See External annotations.
The remaining routes support the bundled browser UI. They can change with a Plannotator release, and the available set depends on the session mode.
Common route families
Availability varies by session mode.
Unknown
/api/* routes return a JSON 404 response rather than the browser application HTML.
Plan review routes
Plan sessions expose routes for the current plan, previous versions, approval or denial, draft annotations, references, uploaded images, saved notes, and plan history. The decision routes are called by the UI and return their result to the agent process that started the session.Document annotation routes
Document sessions expose routes for source content, versions, source-file saving, drafts, references, uploads, feedback, and sharing. Raw local HTML also uses a restricted asset route to load supported files from the HTML file’s directory. Assets outside that directory are refused.Code review routes
Code review sessions expose routes for:- diffs, commits, file contents, and diff-scope switching
- staging and viewed-file state when supported by the repository provider
- GitHub pull request and GitLab merge request context
- pull request comments, artifacts, stacks, and revision selection
- semantic diff and code navigation
- Ask AI sessions and launched review jobs
- review skills and capabilities
AI routes
Sessions with AI support can exposeGET /api/ai/capabilities, session management, a streaming query route, abort, and permission-response routes. Code review sessions can also expose job, job-event, review-skill, and capability routes.
These routes run local agent tools and may ask for permission. Do not proxy them to another user or network.