Reticle Docs: verification for AI coding agents

reticle init is the one command a person runs before anything else. It inspects the directory it is standing in, works out the framework, and writes every piece of wiring Reticle needs: the MCP server registration, the agent rule files, the dev dependencies, .reticle.json, and the bundler plugin.

npx reticle init [--dry-run] [--port N] [--no-mcp] [--no-install] [--app <dir>] [--yes]

Flags

Flag	Type	Default	What it does
`--dry-run`	boolean	`false`	Print the full plan and write nothing
`--port N`	number	unset (resolves to `4400`)	Bridge port to write into the config
`--no-mcp`	boolean	`false` (MCP is registered)	Skip the MCP registration and the agent rule files (`CLAUDE.md`, `AGENTS.md`, `.cursor`) and the `/reticle` command
`--no-install`	boolean	`false` (deps are installed)	Skip the dependency install step
`--app <dir>`	string	unset	Pick which app to wire in a monorepo, without changing directory
`--yes`	boolean	`false`	Accepted for scripting. `init` has no interactive prompts today, so it is a no-op

--no-mcp skips more than the server registration. The agent rule files and the /reticle command go with it, because all three only make sense once the tools are reachable.

What it prints

A plan, one line per step, each with a status mark: ✓ written, · already in place or left alone, ⚠ needs a hand. Captured from a real run inside apps/bench-app:

reticle init (dry run, no files written)
  in /Users/you/reticle/apps/bench-app

  [·] MCP server (Claude, global) → global (claude user scope)
      reticle already registered (install once, used by every project)
  [·] MCP server (Cursor, global) → /Users/you/.cursor/mcp.json
      reticle already in Cursor global config
  [⚠] MCP server (Codex CLI) → /Users/you/.codex/config.toml
      add this to /Users/you/.codex/config.toml by hand:
      [mcp_servers.reticle]
      command = "npx"
      args = ["@reticlehq/server", "mcp"]

  [✓] Agent verification rule → CLAUDE.md
      teach the agent to verify features with Reticle after building them
  [✓] The /reticle command → .claude/commands/reticle.md
      type /reticle to verify one flow in the browser
  [✓] Install dependencies → package.json
      pnpm add -D @reticlehq/react@2.8.0 @reticlehq/vite-plugin@2.8.0
  [✓] Reticle config → .reticle.json
      write project config (framework + port)
  [✓] Vite plugin → vite.config.ts
      add reticle() to plugins (also injects connect())
  [·] Capabilities + store → src/reticle-dev.ts
      file exists, left alone, it is yours to edit

Restart `vite`.

Run from a workspace root with several apps, it refuses to guess and names them instead:

Several apps found in this workspace. Re-run `reticle init` inside the one you want:
  packages/next
  packages/vite-plugin
  apps/atlas
  apps/bench-app
  ...

Or name one without changing directory:  reticle init --app packages/next

Exit codes

Code	Meaning
`0`	The plan ran. Steps marked `⚠` still need a hand, and do not change the code
`1`	Init failed, or an unknown flag was passed

Worked example

cd apps/web
npx reticle init --dry-run     # read the plan first
npx reticle init               # then run it
npx reticle status             # confirm the app actually connected

The install, step by step

What each step writes and how to read the four status marks.

Last modified on August 15, 2026

⌘I