Auto hands a whole goal to the Lead. Start a task in Auto mode, or turn on ❯ Auto in the command bar, and write what you want in a sentence. The Lead picks the roles and skills it needs, builds ordinary workflows for the parts of the goal, runs them, reads the results and chooses the next part, until every part is verified. You can keep talking to it while it works.
- RigOne decides when work is verified, not the Lead. A part counts as done only when its checks and review prove it. A review that fails reopens exactly the result it judged. Work the Lead does itself shows as "Lead says done · not verified" until an independent review and the checks pass.
- Results arrive as in any run. Auto's workflows work in their own copies, and the result is committed with a conventional message. Pushes and pull requests are checked against the GitHub account chosen for the project and show "Pushed as …". An Auto step uses that account only when its agent's More settings has Allow GitHub writes in Auto on.
- The plan shows the parts. With Auto on, the plan column is Agents & work: each part of the goal with its state — waiting, running, ready to verify, completed, needs repair — and where its code was saved. The header counts how many parts are verified.
- Saved goals. A goal is saved where it reached. Resume a goal lists the saved ones. Each task runs its own goal; up to three goals work in one folder at a time, and more wait their turn.
- When the Lead stops early. A Lead that stops while its goal still has work and nothing is running starts again on its own, spaced out and at most three times without progress.
Taking over, pausing and stopping
- Take over stops the Lead's current reply. The goal keeps going, and the Lead comes back when there is work for it.
- Stop ▾ → Pause Auto starts no new work until you press Resume; running workflows finish.
- Stop ▾ → Stop Auto says how many workflows it will end and asks first. The goal is saved where it reached.
Full access
The switch beside ❯ Auto reads Full access or In its own copy, and Settings → Auto
holds the same choice. With full access (the default), the Lead and every step run the way the agent
app runs in your terminal: no fence around the step's copy, no approval prompts, and your normal
environment, so a step can run the whole test suite, use your keychain, SSH agent and Git settings,
and publish. The Lead also gets your own tool servers, and on Claude Code your signed-in Chrome.
In its own copy, the steps stay fenced in their copy and writing outside it needs your approval.
Either way the project's deny rules, the GitHub account check and keeping secrets out of command
lines stay in force.
In Auto the Lead can give a step any Connection you have turned on. A Connection you turned off stays off, and a plan that names it is refused by name.
Needs you
Every decision that waits for you sits in one list, Needs you. Each card says what it is about and what happens after each answer; answers are numbered, some cards take your own words, and a question can be dismissed, which the Lead hears. A decision is repeated once an hour, at most three times. When RigOne is not in front, macOS tells you a decision is waiting, or that a goal finished or stopped, and the Dock icon shows how many decisions wait.
| Card | Asks |
|---|---|
| Question | What the Lead or a planner wants to know |
| Approval | Let a part write outside its copy? |
| Exclusion | Leave a part out of this goal? |
| Retry | Allow one more try? |
| Checkpoint | A step in the workflow that asks you |
| Design review | Accept the look of a changed screen, or mark changes |
| Failing tests | A check failed on tests this goal did not change: fix them here, move to the latest main, or pause |
| Usage limit | Wait for the reset, or use another agent app? |
| Changed definitions | Admit agents or workflows that changed while the goal ran? |
| Same requirement failed | Three tries in a row failed on one requirement: accept with a recorded gap, try once more, carry it to the next stage, or exclude the part |
| Recorded gap | Accept a part with a gap that stays in the goal summary? |
Design review. When an Auto result changes screens, RigOne shows you the tester's screenshots before the result is recorded. Press I accept, or Mark changes: click a spot on a screenshot, write what should change and Send remarks. The Lead turns each remark into the next repair. Turn the review off in Settings → Auto.