reticle affected

List which saved flows must re-verify for a set of changed files.

reticle affected answers one question: given these changed files, which saved flows cover them? It is the foundation the gate and watch are built on, and it costs your agent nothing per turn because it runs in the environment.

npx @reticlehq/server affected [--since <ref>] [file...]

Arguments and flags

Argument	Type	Default	What it does
file...	strings, positional	none	Explicit changed files
--since <ref>	string	HEAD when no files are given	Also include files git reports as changed since this ref

With nothing after it, reticle affected means the working tree against HEAD. It used to be a usage error, while the rule reticle init writes into the agent’s own instruction file told the agent to run it.

What it prints

One reticle_affected line. Real capture from this repository, with the file and flow lists trimmed for length:

{
  "t": "2026-08-14T19:38:46.407Z",
  "event": "reticle_affected",
  "changedFiles": ["docs/cli.mdx", "packages/server/src/tools/e2e-surface-drift.test.ts"],
  "affected": ["deploy-journey", "verify-route", "console-compose"],
  "unknownProvenance": ["deploy-journey", "verify-route", "console-compose"]
}

Field	Meaning
changedFiles	The resolved file set: your positional arguments plus whatever --since added
affected	Saved flows that cover at least one of those files
unknownProvenance	Flows with no recorded source mapping. They are listed as affected because the safe assumption is that they might be

Exit codes

Always 0. A load error is logged as reticle_affected_failed, not thrown. Use reticle gate when you want a non-zero exit.

Worked example

npx @reticlehq/server affected --since origin/main
npx @reticlehq/server affected src/components/Login.tsx