Search documentation
The durable search route: every result the overlay can show, plus the full route index when JavaScript is off.
The query field above searches every page. Every documentation route is listed below, grouped by section, and that list works with JavaScript off.
Start here
- Start here Get from nothing to a running channel: install the CLI, join or set up a workspace, and create your first channel.
- Your first melt Create a Feature delivery channel, watch Forge and Probe work, answer when an agent asks you to, accept a doc suggestion, and take the change to review.
- Joining a workspace Someone set this workspace up before you arrived: what you are looking at, which parts are yours, and what to do first.
- Set up your workspace The admin's first quarter hour: find the compute provider and invitation panes, read the agent roster each template brings, and create the first channel.
- Install the CLI One command puts the `crusible` binary on your machine, after it verifies the release signature and the checksum in front of you.
Concepts
- Concepts What a channel is, who holds the record, and how a surface answers to the conversation that opened it.
- Channels are units of work A channel is a feature, an incident, a research question or a machine, with a state, a branch, agents and surfaces of its own.
- The conversation is the record Everything that happens to a piece of work lands in its conversation, with a priority, as a card rather than a paste, and with every decision on record.
- Every surface has a provider Behind every surface is a provider that holds its data, and connecting a tool you already use changes one surface and nothing else in your workspace.
- Surfaces answer to the conversation A surface opens because the conversation pointed at something, steps aside when you are done, and that is why the header shows chips and not tabs.
- Agents are teammates An agent has a profile, running instances, per-channel permissions and a cordon control; it proposes, a person decides, and the record shows who did what.
Guides
- Guides Steps for someone who already knows what they want — grouped by the job you are on, not by the surface you happen to be in.
- Create a channel Pick the template that matches the work, read what the preview promises, and create a channel with its surfaces, agents and workflow already wired.
- Go solo Give the conversation the whole window when talking is the work, and give the surface the whole window when looking at one thing is the work.
- Set the signal dial Choose how much agent traffic a channel shows you, read what the dial is holding back, and open a rollup to check nothing was dropped.
- Direct a message to one agent Scope your next message to a single agent with the Direct to rail, without leaving the channel, and know when a direct message is the better place.
- Act on a pending-decision card Find the card an agent is waiting on, read its ranked options, choose one or answer in your own words, and put the run back in motion.
- Review agent suggestions in docs Open the suggestions waiting on a doc, read each one beside the text it changes, and accept or reject it block by block.
- Review a pull request Open the Review surface, read a pull request against its checks and its reviewers, and take a machine on that branch when you need to run it.
- Have an agent operate a connected tool Ask an agent in the channel to file the issue, open the pull request or write the page in the tool your team already keeps that work in.
Reference
- Reference Every surface, provider and bridge Crusible documents, plus the flat pages that belong to no family.
- Surfaces Every surface, what each one shows, and which channel kind turns it on.
- Terminal A live shell on the channel's worktree, driven by the people and agents attached to it, on a machine Crusible provisions and keeps running.
- Project The channel's mounted repositories, a file tree and an editor, plus the diff that the work in this channel actually produced.
- Docs A block document for the channel, where an agent's writing arrives as a suggestion and a person decides whether it becomes part of the document.
- Forge The repository itself — branches, commits, tags and releases — sitting in the channel whose work produced them.
- Providers What each surface ships with by default, and which providers you can connect instead.
- MCP Model Context Protocol is one of the two ways a tool becomes the provider behind a surface. Here is what an MCP connection gives you.
- Notion Notion as the provider behind the Docs surface: Notion keeps the pages, and agents operate them through Notion over MCP.
- Linear Linear as the provider behind the Issues surface: Linear holds the issues, and agents operate them through Linear over MCP.
- GitHub GitHub as the provider behind the Review surface: GitHub holds the pull requests, and agents operate them through GitHub over its API.
- Sentry Sentry as a provider behind the Dashboards surface: Sentry holds the errors, and agents operate them through Sentry over MCP.
- Bridges What a bridge is, how it differs from a provider, and the tool Crusible bridges into.
- Slack What a Slack bridge is for: relaying a channel's conversation both ways with an origin badge, and leaving the record in Crusible. Not a provider.
- Composer The message box: slash commands, @ mentions of people and agents, # references to files and pull requests, and the Direct to rail.
- States and priorities The words Crusible uses for what is happening: the four message priorities, the state lexicon, the channel status chip and the signal dial.
- Glossary Every coined word in these docs, defined once: channels, surfaces, providers, agents, priorities and whose store holds the record.
- Verify a download What a Crusible CLI release contains, what each checksum, signature and attestation proves, and what it means when one of them does not match.
Troubleshooting
- Troubleshooting Symptoms you can see right now, matched to the fix — a machine that idled out, a channel stuck at blocked, a connection that failed.
- A machine shows “Lost the link” Crusible dropped the connection to a machine and is retrying. What is safe, what to read while you wait, and when to bring in an admin.
- A machine idled out The machine suspended after a quiet spell and its state was saved. What that message means in plain language, and how to bring the machine back.
- A run is stuck waiting on a person An agent asked a question and paused, or the run reached a human gate. The two places that card hides, and how to put the run back in motion.
- A channel shows “Blocked” The channel's state says something in it is waiting. How to read what it is waiting on, and which of the two causes you are looking at.
- A message is missing from a channel The signal dial folded it. Where the rollup sits, how to open it, and the guarantee that nothing in the conversation was thrown away.
- A connection failed or lacks a scope A surface shows nothing from the tool behind it, or an agent cannot reach it. What a connection row is for, and who fixes which half.
- A control in a guide is not visible A guide names a button that is not on your screen. The three reasons a control is hidden from you, in order, and who can turn it on.
Admin
- Admin Set the workspace up, connect tools, decide what agents may do, and run it day to day.
- Connect a compute provider Where the machines a workspace runs on are connected — Cloud, Docker, Kubernetes or SSH — and what the Providers pane under Account is for.
- Invite people and set roles Bring people into the workspace and read the role each one holds, from the Directory pane under Account in Settings.
- Connect a provider Where an outside tool is connected to the surface it backs, how it is authorised, and what settles the writes agents may make to it.
- Switch a surface's provider How a surface comes to point at a connected tool instead of Crusible's own store, or back again, without touching the channel or its conversation.
- What agents can see and do What an agent reads in a channel, what it may write, where its work is recorded, and what a cordon stops.
- Settings The two Settings scopes — what is yours alone, and what belongs to the workspace — and what each pane in them is for.
- Roles and permissions The workspace roles the product shows, the channel-level Access rows, and which of the two decides what.