The console Live · by invitation
Where the work lives, and where the approvals land
Enforcement stays on your machine; this is everything that has to outlive it. One line from anywhere lands in Triage, a request for a wall to move arrives with its reason attached, and the trail keeps its shape after the laptop is gone.
✓ gate: four fields answered, no high-risk zone to approve
REQ-7 · schema · write · CC-42
Reason: the board query needs an index
Instead: hand the DDL to the owner
1 hour4 hoursUntil the task closes
✓ Approved — schema is open to CC-42 for 4 hours
In the console a task crosses the gate into In Progress, and a zone’s owner answers an access request — for one hour, four, or until the task closes.
What it is for
- Capture, from wherever you are. One line reached Triage 4.0 seconds after the click — with the typing scripted, measured once, on 2026-08-04, for one task.
- The approval moment. A zone's owner sees what is being asked, why, and what the agent would do instead — then answers in one tap, with a clock attached to the yes.
- The trail past one machine. By default a close from the CLI writes its record into your repository, where it survives uninstalling us. The board keeps a copy of each, and the only copy of the record when the console or a merge did the close, which
cycle export --auditshands you as Markdown; it is what makes the trail legible to someone who is not standing at that checkout.
Getting in
Access is by invitation while this is new. That is a real queue rather than a coming-soon page: the product runs today, and the invitation is about how fast it grows, not about whether it exists.
Already have an account? Sign in.
What it deliberately will not do
- It will not close a task without a merge GitHub confirmed. It closes one once GitHub reports its pull request merged, against the files the hand-in recorded from git or, without them, the merged pull requests' own files — through the same gate as the CLI; otherwise it refuses and points to
cycle verify --closeon the branch. Where the board's GitHub App is installed, a merge closes its task through that same gate on its own — on GitHub's webhook, or on the sweep the board runs every 15 minutes (CC-1346). - It is not in the deny path. The hook decides locally, with no network call in the decision, so an outage here cannot open a zone — and cannot shut one either.
- It does not run your agents. Nothing is executed here. This is the board, the owners and the record.
The local half arrives with the plugin or the CLI, and the model they all read is the zone map.
Questions this page answers
Can I approve an access request from the console?
Yes, and it is the stronger of the two doors — the audit trail records which one answered. It can also close a task, once GitHub has confirmed its pull request merged and the board can name the files — from the hand-in's recorded diff, or else from the merged pull requests; otherwise it refuses and points you to cycle verify --close on the branch.