reticle try is the fastest way to see Reticle on your own app. It drives a URL once with the Reticle Harness, in a browser window you can watch, and ends with a list of the journeys it tried and how each one ended.
The app needs nothing installed. A page with no Reticle SDK gets one supplied for the drive, so verdicts cover the DOM, network, console and routes. There is no component state and no source file:line until you run reticle init.
Sign in first
The drive runs on the Reticle platform, so try needs a linked folder. On a machine that is not linked it drives nothing and says:
Run reticle connect in the folder, then run try again. It exits 1 in this case.
Arguments and flags
What happens
try asks the platform for one free drive. If the workspace needs a card first, it prints the platform’s message and the plan page, then exits 1 without opening anything.- It opens the URL in a window you can watch, through the Reticle daemon, and starting one if none is running.
- The Harness drives for up to two minutes and 40 steps, and records what it drove as saved flows.
- It prints the result and sends the run to your dashboard, the same way
reticle push does.
What it prints
Each verdict comes from the engine. A journey that neither passed nor failed is reported as not proved. It is never counted as working.
If the run could not be sent, try says so, keeps the run on this machine and tells you to run reticle push. It never prints “Saved” in that case.
Exit codes
Last modified on October 9, 2026
