reticle watch

Watch the working tree and report which saved flows must re-verify on every save.

reticle watch is the buddy loop. It watches the current directory and, on every save of a source file, reports which saved flows the change puts at risk. It runs in the environment, so it costs your agent nothing per turn.

npx @reticlehq/server watch [url]

Long-running. Stop it with Ctrl+C.

Arguments

Argument	Type	Default	What it does
url	string, positional, optional	unset	Accepted by the parser and reserved for the increment that replays the affected flows against a live app. The current version detects and reports only

What it watches

The working directory, recursively, filtered to .ts, .tsx, .js, .jsx, .mjs, .cjs, .vue and .svelte. Changes are batched with a 200ms debounce.

What it prints

Real capture, the first two lines of a run in this repository:

{"t":"2026-08-14T19:39:09.196Z","event":"reticle_watch_started","cwd":"/Users/you/reticle"}
{"t":"2026-08-14T19:39:09.278Z","event":"reticle_buddy","status":"✓ 13/47 flows nominal · 9 flaky quarantined"}

Event	When
reticle_watch_started	Once, at startup, with the directory being watched
reticle_buddy	Once at startup and after every batch. One ambient line, designed to be parked in a status line
reticle_watch_affected	After a batch, when at least one flow is affected. Carries changed and affected
reticle_watch_failed	A flow load error. Never fatal

The buddy line is deliberately best-effort and silent on failure. A status line that throws is worse than no status line, and it must never interfere with the watch loop it rides on.

Exit codes

Runs until interrupted.

Worked example

npx @reticlehq/server watch &
# edit src/components/Login.tsx, and the affected flows are named on save