Terminal
A shell that outlives the tab it was opened in.
Close the laptop, change network, redeploy the broker — the session keeps running. The agent's scrollback is authoritative, so nothing depends on your connection staying up.
How it answers to the conversation
The command ran here, so the channel has it.
The shell is attached to the channel, so what an agent ran is readable a month later — no asking around, no archaeology.
Driven by
The strip above the prompt names every agent currently attached. Two agents on one shell is normal, and you can see it.
Collapsed output
A thousand lines of build output become one row — timestamp, truncated command, exit code, duration. Expand the ones that matter.
The status bar
Branch, runtime version, uncommitted count, and a Cruising indicator when automation holds the shell.
Risk classification
Every command is classified as it runs, so a session replay shows you the four that touched production rather than all four hundred.
What it does
Three things this surface is for.
One microVM per worktree
Not a shared container with a directory each. A golden-snapshot clone brings a worktree online in about 150 milliseconds, and hibernation is a VM suspend that keeps your processes alive.
A broker in the middle
The agent dials out; the broker proxies and caches the live session. A dropped client is a non-event rather than lost work.
Agents share the prompt
An agent runs a command, you take over mid-session, it picks the thread back up. Same shell, same history, both authors visible.
Yours or ours
What is underneath.
Crusible provides this one. There is nothing to connect.
Crusible provisions the machine itself — that is what lets a shell outlive your laptop and your network.
Where it appears
Channels that expose this surface.
Worktree and workspace channels get a shell. A planning or analytics channel has no use for one, so it does not.
- Terminal A shell on a worktree, in the channel that needs it. Built in
- Project Mounted repositories, a file tree, and the diff that matters. Built in
- Review A pull request opens in the channel that produced it. Built in, or connect GitHub, GitLab
- Flow Agents, CI jobs, a human gate and a deploy — peers in one graph. Built in
Division of labour
What agents do here, and what needs a person.
Agents run the loop
Install, build, test, reproduce, bisect. The whole tight loop happens in the worktree the channel owns.
Agents hand back
A command an agent's permission set does not cover stops and becomes a decision card, with the exact command it wanted to run.
A person holds the keys
Production reach, destructive commands, and credential access. The cred broker hands out short-lived scoped tokens, never your secrets.
Open a shell where the work already is.
Crusible is opening to teams in private beta.