Skip to main content
reticle gate --list answers one question: given these changed files, which saved flows cover them? The gate checks the same set. --list only names it and checks nothing. It costs your agent nothing per turn because it runs in the environment.
reticle affected is the old name. It still works for one release and prints one line naming gate --list.

Arguments and flags

With no files, reticle gate --list compares the working tree with HEAD.

What it prints

One reticle_affected line. Real capture from this repository, with the file and flow lists trimmed for length:
The real run named 47 flows in each list. The CLI prints this as a single line of JSON; it is pretty-printed here to be readable.

Exit codes

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

Worked example

Last modified on November 4, 2026