Record a journey once, re-verify it forever

Exploring an app to find a journey is the expensive part, and re-driving it with a model pays that cost again on every change. Reticle flows pay it once: the journey is saved with semantic anchors and replayed deterministically afterwards.

Needs Reticle wired in the project. Not set up? Follow the reticle skill: it installs Reticle, asks the user before init changes the app's files, and proves one flow.

Record

You do not have to ask. A drive is saved as a flow automatically when the session ends, written to .reticle/flows/. Commit it: any agent on the repo can then replay it.

What decides whether it is worth committing is how you drove it. A step keeps a consequence only when you declared one, so drive the golden path like this:

reticle_act_and_wait({ sessionId, ref, action: "click", until: { kind: "signal", name: "task:created" } })

That step replays as a test. A bare reticle_act saves a click with nothing to prove, and replays green through any regression.

To name a flow deliberately rather than take the automatic one, reticle_record and reticle_flow_save do it through reticle_run { tool, args }. Neither is advertised, and neither needs to be: reticle_run is on the default surface and dispatches to any registered tool by name. RETICLE_ADVERTISE_ALL_TOOLS=1 advertises them outright, under older, unmerged tool names. Do not set it for an agent: the calls in this skill use the default names.