The verification harness, embedded in the IDE
The Arcus CLI runs from the same terminal, the same hooks, and the same CI you already use. The verdict shows up where you’re already looking, not in a dashboard you have to remember to open.
Deeply embed quality in the developer workflow
A verification harness only earns that name if it runs where the work actually happens. The CLI is how Arcus embeds itself directly in your IDE, the same terminal, the same hooks, the same CI, instead of sitting in a dashboard one tab away from where the code gets written.
The verdict shows up in the same terminal you just committed from, or the same PR check CI already runs. Nothing to log into, nothing to remember to go look at after the fact.
Run it locally mid-session, wire it into a pre-commit hook, or let CI call it on every PR. One command, one verdict format, wherever it runs, not three different places to check whether something passed.
How you’d actually use it
Install it once
One global install, no project config required to get a first result.
Run it against what you just shipped
Point it at a PR, a branch, or nothing at all to check whatever’s uncommitted in your working tree right now.
Watch it run, not just the result
Run a single test locally and watch the agent execute it step by step in your own terminal, not a pass or fail that shows up after the fact.
Read the verdict, not a wall of logs
Gaps, blast radius, and a release confidence score, the same three things the dashboard shows, printed where you’re already looking.
Instantly becomes a test QA can run anywhere
That same local run is instantly converted into a deterministic automation script, results included, that QA can execute across real browsers and devices, not just once on your machine.
Fits the pipeline you already have
It’s a CLI first, so it behaves like one: scriptable, exits non-zero on a failed gate, no dashboard login required to get a result. Call it from wherever you already run checks.