Project
The files the conversation is about.
Every channel that does code owns a worktree, and Project is the window onto it. Browse it, read the diff, see which agent touched what — without leaving the conversation that explains why.
How it answers to the conversation
A path in the transcript is a link into the tree.
An agent that mentions a file gives you the file. The diff it produced arrives as an artifact card, and the card opens here.
Mounted repositories
One channel, several repositories. The selector in the status bar says which ones, and a change can span them.
The modified marker
Uncommitted work is visible in the tree, so you always know whether what you are reading is on the branch yet.
Attribution per change
Who wrote this line — which person, or which agent instance. The answer is in the gutter, not in a git log you have to go and read.
Browse and diff fidelity
Deliberately not a full IDE. Read, compare and navigate here; the heavy editing happens in your own editor against the same worktree.
What it does
Three things this surface is for.
One worktree per channel
The channel's files are its own. Two channels working the same repository do not step on each other, because they are not sharing a checkout.
The diff, in context
A change opens beside the conversation that asked for it, so review starts from intent rather than from a list of hunks.
Your editor still works
The worktree is a real filesystem behind a real broker. Attach your own editor to it and nothing about the channel changes.
Yours or ours
What is underneath.
Crusible provides this one. There is nothing to connect.
The worktree is Crusible's own filesystem — that is what lets every channel own its files.
Where it appears
Channels that expose this surface.
Worktree, feature and incident channels. A roadmap channel has no filesystem, so it has no Project surface.
- 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 edit
Directly, in the worktree, with every change attributed to the instance that made it.
Agents explain
A diff arrives with the reasoning attached in the channel, not as a bare patch you have to interpret.
A person merges
Getting onto a protected branch runs through Review, and that gate is a permission an agent either has or does not.
Put the files next to the reason for them.
Crusible is opening to teams in private beta.