Resetting the console¶
Everything on this page is in the console under Settings → Reset. None of it needs a terminal, and none of it deletes anything: a reset moves what it takes into a restore point, listed at the foot of the same screen, and every one of them can be put back — including the full factory reset.
Each tier asks you to type a phrase before it runs, on top of the usual one-shot code. That is deliberate: a reset should cost you a moment's thought, not one click.
The six tiers¶
| Tier | What it removes | What survives |
|---|---|---|
| Look and layout | The theme, lens and layout you last used, the tour, and the window's cached shell. This device only. | Everything. No company data is touched. |
| The work | Every item on every pipeline in every cell and its attachments, the Desk queue, the build queue, every run record, log and trace, and everything the agents have written into their memory stores. | The company itself — cells, pipelines, workloads, people and rules — the connections, everyone's sign-in, and the audit log. |
| The company | Every cell, pipeline, workload, agent, rule and workforce chart, your answers to the first-run interview, and the work above, because it belongs to those cells. The scheduled workloads are stopped and removed from the machine. | Your sign-in and everyone else's, the connections, and each cell's read-only copy of its books. |
| The connections | Every seat, model account, key and local engine; the channel credentials for email, chat, the code host and the vault; the offsite backup key; the address this console is published on. | The company and all of its work, and everyone's sign-in. |
| The people | Every user but you and their per-cell membership, the Google and Microsoft sign-in registrations, every app key another program uses, and every signed-in session — including the one you are using. | Your passphrase and second factor, and the company. |
| Everything | A factory reset. All of the above, plus your passphrase and second factor, the audit log, the console's own telemetry, each cell's copy of its books, the local backups and your licence key. | Nothing but the restore point it writes — which holds every one of those. |
After Everything, the console reopens the first-run interview, exactly as it did on the day it was installed. Sign in again by claiming it with a new passphrase, and set the company up from scratch.
What stands in the way¶
The screen lists blockers before it lists tiers, each with the one control that clears it:
- A workload is running. Resetting under it would move the state it is writing mid-sentence. Stop it from the button on the blocker.
- An earlier reset stopped part-way — a machine that lost power, a window closed mid-request. Some of the install is already in that restore point, so put it back first and start again.
Putting one back¶
Every reset appears under Restore points with its tier, its size, when it ran and who ran it. Restore puts the whole thing back where it came from.
A restore refuses rather than merging: if anything has been created since with a name the restore point also holds, it stops and says which. Move that aside — or reset that tier again — and restore then.
Delete destroys a restore point for good. It asks you to type the restore point's own name, because it is the only control in the console that truly destroys anything: after it, whatever reset produced that point can never be undone.
What a reset never touches¶
- The Claude Code sign-in on this machine. It lives outside the console and is ended from the Seats board, not here — so a factory reset leaves the machine signed in to Claude Code, and you sign that out separately if you are handing the machine on.
- Anything on the code host. Resets are local to this machine. A repository the console pushed to keeps everything it was given; delete it there if you want it gone.
- Your licence entitlement. The full erase archives the key file, so re-enter the key afterwards (or restore the point) — the licence itself is unaffected.