Lanes
How Lanes will keep every agent seat in view, bring the questions that need you to the front and carry messages between agents and people.
On this page
Lanes is where you sit. It keeps every lane in view with its state, brings what needs you to the front, and carries messages and decisions between agents and people. Rocket! plans and does the work; Lanes presents and controls it without owning the engine. Lanes never runs a model, never holds a credential and never records whether a result is accepted. This page explains lanes, attention, decisions and messages, and what the first release includes. All of it is Planned.
The Lanes you use today, Lanes 1.8, keeps running unchanged. The Hypervibe Lanes described here replaces it in one switch, and only after it passes a parity check over the same scenarios and Christian approves the switch. Until then the new Lanes runs beside 1.8 and changes nothing there. Lanes keeps working with tmux and Zellij terminals until its own terminal hosting passes the same check.
A lane is one addressable work seat #
| Term | Meaning |
|---|---|
| Lane | One addressable work seat. It outlives the processes behind it, and closing its view detaches without stopping the agent |
| Session | Rocket!'s resumable journal of the agent's work. After a kill it resumes as the same session |
| Workspace | The governed container of lanes, repositories and identities. Its configuration lives in the Platform |
| Address | A lane's name inside its workspace, used for messages |
| Coordinator | The one lane each workspace names to receive its needs |
| Tile | A live terminal view of one pinned lane |
You attach and detach without stopping the agent #
In the first release, Lanes shows one Rocket! session full screen in the planned hyper command, with no sidebar. Detaching closes the view and never stops the engine. Re-attaching repaints from where you left off, with no duplicate effect. In the first release's team record, you can attach to a session on another machine through the team server, and revoking your device or membership closes a live attachment.
Tiling comes in a later release. Home shows every lane you pinned as tiles, with Needs you above them. The directory lists lanes in sections: Needs you; Working; Done, not seen; each workspace; and Unregistered, for running terminals that are not lanes yet. One layout engine serves the terminal and the web, and a layout never starts, stops or resizes an agent. Type here gives a tile the keyboard, and Leave terminal returns it.
Needs you puts every open question first #
Each lane shows one of seven statuses: Needs approval, Needs input, Working, Done, Errored, Shell or Idle. Needs you gathers the lanes with an open decision, an approval or input prompt, or an error to act on.
A decision is a question with two to four options. The agent's pick is tagged and never preselected. The answers to a decision are Approve, Reject, Choose or Details, and the answers to a tool permission are Allow once, Allow always, Deny or Edit. An answer goes to the item's authority, which commits the first answer it receives; another surface then reads "answered elsewhere". Lanes never answers by typing into a terminal. Where an agent client has no answer channel, the answer stays visible but disabled, with the reason, and you answer in the lane.
Lanes also shows the Result card and routes Accept or Reject to Rocket!'s engine, which records the receiver's decision through shared Work, the one owner of tasks and runs, apart from the verifier's verdict. A later release adds the owner's decision list: one list of every open item addressed to you, your teams or your roles, in the terminal, on the web and on the phone.
Messages go to an inbox and never into a terminal #
A message is one entry delivered to a lane's inbox. It is never typed into the lane's terminal, and it is never consent or an instruction the agent must follow. Needs travel from a lane to its workspace's coordinator, then to the one fleet admin lane for the whole site.
In the first release, no message path types into a terminal. A later release adds typed messages that notify, ask or carry a decision, with delivery recorded in five steps. No step proves a later one:
- Accepted into custody.
- Delivery attempted.
- Accepted by the agent's client.
- Acknowledged by the recipient.
- Work outcome reported.
A delivery Lanes cannot confirm reads Not confirmed yet, and Lanes never retries it on its own.
Schedules, pages and the phone come later #
| Area | First release | Later releases |
|---|---|---|
| Sessions | One full-screen Rocket! session, attach and detach | Tiles, Home and the directory, in the terminal and on the web |
| Attention | Approvals, decisions and the Result card inside the session | The owner's decision list, with escalation |
| Messages | No message typed into a terminal | Typed messages with delivery receipts |
| Schedules | Not included | Standing responsibilities that wake on a condition and can be paused |
| Pages | Not included | Revisioned HTML or Markdown pages, private by default |
| Phone | Not included | The companion, through the Lanes relay |
A page's content stays on its owner's machine, and a page that looks like it carries a secret is refused. A schedule names who owns its unresolved work. On the web, Lanes is one of two areas, beside the Platform.
Where to go next #
- Rocket! does the work a lane shows.
- Companion carries Needs you to your phone.
- Hypervibe platform holds workspace configuration and grants.
- Work and quality covers commissions, verdicts and acceptance.
- Glossary defines the terms on this page.