Skip to main content
reticle mcp is the command your agent runs. It is the MCP server the editor launches: a stdio proxy that bridges the client to the daemon’s SSE endpoint, starting a daemon first if the port is empty.
This is what reticle init registers, so you rarely type it yourself.

​
Flags

​
The rule this command lives by

The proxy is the MCP server the editor launched. Nothing respawns it, so an uncaught throw here is what a user experiences as “the MCP server disconnected”. Three behaviours follow from that:
  • Crash handlers write to the proxy’s own log file, not just stderr, because the editor swallows stderr.
  • A daemon that is not there is not fatal. The proxy answers initialize itself, serves the cached tool catalog, and retries a daemon on every client request. Present and complaining beats absent, because absent needs a human.
  • Reconnect is self-healing: if the daemon exited, crashed, was stopped, or shut itself down as idle, the reconnect path spawns a new one rather than retrying a dead port until the budget runs out.

​
What it prints

Structured lines to the proxy log (~/.reticle/), not to your terminal, since stdout is the MCP transport.

​
Exit codes

Runs for the life of the editor session.

​
Worked example

The tools this exposes

The full surface your agent gets once this is registered.
Last modified on August 14, 2026