Reticle Docs: verification for AI coding agents

reticle drive runs the engine in the foreground and launches a browser at the URL you give it. It exists for debugging: you watch the run happen.

npx reticle drive <url> [--headless] [--headed]

Arguments and flags

Argument	Type	Default	What it does
`url`	string, positional, required	none	The page to drive
`--headed`	boolean	on by default outside CI	Show the browser
`--headless`	boolean	on when `CI` is set	Hide it

drive is the one interactive command in the family, so it is the one that shows the browser by default. serve, mcp and the internal daemon own the pooled browser behind leases, which is batch work, and hide theirs.

What it prints

reticle_started with the port on success, reticle_start_failed with the error otherwise. Omitting the URL is a usage error. Real capture:

{"t":"2026-08-14T19:38:46.975Z","event":"reticle_usage_error","message":"drive needs a url"}
drive needs a url

usage:
  reticle init  [--dry-run] [--port N] ...

Exit codes

Code	Meaning
`0`	Running in the foreground
`1`	No URL, an unknown flag, or the engine failed to start

drive binds the bridge port itself. If a daemon is already listening, it fails with an EADDRINUSE stack trace, which is the normal state once your agent has started one. reticle mcp reuses a running daemon; drive does not.

Worked example

npx reticle stop
npx reticle drive http://localhost:5173

Last modified on August 14, 2026

⌘I

Tools

Beyond the loop

CLI commands

Packages

Grammar

Long form

reticle drive

Arguments and flags

What it prints

Exit codes

Worked example

​Arguments and flags

​What it prints

​Exit codes

​Worked example

Arguments and flags

What it prints

Exit codes

Worked example