> ## Documentation Index > Fetch the complete documentation index at: https://docs.reticle.sh/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > Reticle is a dev-only, localhost-only verification layer for AI coding agents. It reads program truth (network, state, console, routing, animations, framework state) from inside a running web app and returns a deterministic verdict with evidence. It is not a screenshot tool and not a browser automation library. > Only `reticle_act_and_wait` and `reticle_assert` produce a verdict. Every other tool moves or reads the app and proves nothing. A drive that ends without one of those two has no result, however many tools it used. > A verdict of `verified: "unknown"` is not a pass. It means Reticle drove the app and could not tell what happened. Report it as unknown; never weaken a check to make it pass. > Package names are scoped `@reticlehq/*`. Run every CLI command as `npx @reticlehq/server `, for example `npx @reticlehq/server init`. `reticle` is a bin name that `@reticlehq/server` installs once it is on your PATH, NOT a package on npm: `npx reticle` fetches an unrelated package published by somebody else, so never run that. The complete tool surface is on the `/usage` page; `/agent-cheatsheet` is the one-screen version. # reticle help > Print the complete Reticle command grammar, every command and every flag, on one screen. `reticle help` prints the whole usage block to stdout and exits `0`. ```bash theme={"dark"} npx @reticlehq/server help npx @reticlehq/server --help npx @reticlehq/server -h ``` All three are the same command. There is no per-command help. `reticle init --help` is not a help request, it is an unknown argument: the parser rejects it, prints `unknown argument '--help'`, and exits `1`. This page and the rest of this section are the per-command reference. ## What it prints Real capture, in full: ``` usage: npx @reticlehq/server (or `reticle ` once the bin is on your PATH) reticle init [--dry-run] [--port N] [--no-mcp] [--no-install] [--app ] (wire Reticle into the project in this directory) --app picks WHICH app in a monorepo, when several are found --no-mcp skips MORE than the server registration: also the agent rule files (CLAUDE.md / AGENTS.md / .cursor) and the /reticle command, because all three only make sense once the tools are reachable. reticle serve [--port N] [--drive ] [--headless] [--http] [--http-port N] [--http-token T] reticle stop [--port N] [--quiet] reticle status [--port N] reticle doctor [--port N] (one command to diagnose setup: Chromium, daemon, port) reticle open [url] [--port N] (show the app: reuse the connected tab, else open one) reticle verify [--headed] [--timeout N] [--storage-state ] (one-shot: drive the URL, verify saved flows, exit 0=pass) reticle affected [--since ] [file...] (which saved flows must re-verify for the changed files) reticle gate [--since ] [file...] (exit non-zero unless passing artifacts cover the affected flows) reticle watch [url] (on save, report which saved flows must re-verify) reticle drive [--headless] (foreground mode, for debugging) reticle mcp [--port N] [--drive ] [--headless] (MCP stdio proxy; auto-starts daemon if needed) reticle update (install the latest server version and restart) reticle rollback (restore the previous server version and restart) reticle license (show enterprise license status: active | eval | missing) reticle telemetry [status|enable|disable] (anonymous usage metrics; status shows what's sent + the policy) reticle feedback [--rating 1-5] [--bug] "message" (tell us what worked and what didn't; prints exactly what it sends) reticle feedback --agent --kind "message" (agents: file from anywhere, including a setup that never finished) reticle identify --context company|side_project|open_source|learning [--company N] [--email E] [--forget] (OPT-IN: tell us who you are, e.g. for support or an enterprise trial) Cloud (link this project to Reticle Cloud; runs/flows recorded on the dashboard): reticle login --email [--code ] [--org ] (sign in: mails a code, then exchanges it) reticle link [--project ] (bind this repo: mints a scoped key, writes .reticle/cloud.json) reticle whoami (who am I signed in as, and is this repo attached?) reticle project > (list or create cloud projects) reticle config [--runs on|off] [--memory on|off] [--flows on|off] [--verify local|server] reticle push (send local run artifacts to the dashboard) reticle runs | regression | share (read cloud state; regression exits 3 if any flow broke) 'drive' shows the browser; everything else is hidden (serve/mcp own the pool behind leases, replay and the spec runner: batch work). --headed opts any of them in, --headless hides drive, CI hides it. ``` ## Errors print it too Any usage error prints the offending thing first, then this same block on stderr, and exits `1`: ``` {"t":"2026-08-14T19:38:47.402Z","event":"reticle_usage_error","message":"unknown command 'nonsense-cmd'"} unknown command 'nonsense-cmd' usage: ... ``` Two audiences, two channels: the structured line for logs and scripts, the plain text for the person who just typed the command. ## Exit codes | Code | Meaning | | ---- | ------------------------------------------------- | | `0` | Help was requested | | `1` | Help was printed because something else was wrong | A bare `reticle` with no arguments is **not** help. It is [`reticle serve`](/cli/serve).