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.
- Your first worktree channel Open a worktree channel on a branch, work in its live shell beside the conversation, and hand the branch to an agent. Planned · Phase 2
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.
- The signal dial compresses, never drops Why attention is a control in the channel header, what each of the four levels holds back, and why a person is never folded. Planned · Phase 2
- Agents propose, a person decides Where a person sits between an agent's work and the change it would make, and what it costs to move one of those gates. Planned · Phase 2
- A bridge carries conversation, not a surface What a bridged channel relays, why the record stays in Crusible, and why a bridge is never the provider behind a surface. Planned · Phase 3
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.
- Change a channel's surfaces Choose which two surfaces a channel leads with, reach the rest behind the switcher, and turn a surface on or off for the channel. Planned · Phase 2
- Use the task board Open a channel's board, read what each task is waiting on, and follow a task through to the surface that holds its work. Planned · Phase 2
- 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.
- Archive a channel Close a channel whose work has shipped, and keep its conversation, its decisions and its artifacts readable afterwards. Planned · Phase 2
- 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.
- Mute one agent Quiet a single agent in one channel from the volume controls, without changing the level the channel shows you. Planned · Phase 2
- Read rollups and digests Open a folded run of agent updates, read a channel's digest, and know what each one is standing in for. Planned · Phase 2
- Work the inbox Clear the notification inbox in order: what leads with a status chip, what is only an update, and where each entry lands you. Planned · Phase 2
- 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.
- Check an agent's cost and context Read an agent's profile: its running instances, their context meters, and the uptime, tokens and cost it has run up. Planned · Phase 2
- Cordon an agent Stop new work routing to an agent while it finishes what it is already holding, and lift the cordon afterwards. Planned · Phase 2
- Set agent permissions in a channel Read and change the Access rows that govern what agents may do on one channel's work, and know which two remove a person. Planned · Phase 2
- 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.
- Replay a test run Step through a captured run beside its replay, read the agent's commentary on each step, and reveal masked data when you must. Planned · Phase 2
- Trace a run in Flow Follow a run through the orchestration graph: which node is running, which gate is waiting, and what a failed node logged. Planned · Phase 2
- Replay a session Scrub through a past terminal session command by command, and read what each command did and how risky it was. Planned · Phase 2
- 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.
- Work in a surface backed by an external tool Use a surface whose provider is a tool your team already runs, and know which actions land in that tool rather than here. Planned · Phase 2
- See which provider a surface is using Find out which tool holds the data behind a surface, and who in your workspace connected it. Not yet documented
- Bring existing work in Start working in Crusible on a repository, a project or a document set your team already has, without moving any of it. Planned · Phase 2
- Work in a bridged channel Post into a channel relayed from Slack or Teams, read the origin badges, and know which of your actions reach the other side. Planned · Phase 3
- Work with a partner org Share a channel with another organisation, read who is outside your workspace, and keep internal work in a channel that is not shared. Planned · Phase 3
Reference
- Reference Every surface, provider, bridge and agent, plus the flat pages that don't belong to one of the four families.
- 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.
- Review A first-party git host is planned. Today Review runs on GitHub or GitLab, opening a pull request in the channel whose work produced it. Planned · Phase 1
- Dashboards Crusible's own boards are planned. Today Dashboards runs on the tools you already have, putting errors, service health and analytics on one board. Planned · Phase 1
- Issues An issue filed from the channel that found it and assigned to an agent, with Linear as the connected provider that holds it. Not yet documented
- Diagrams A canvas that people and agents draw on at the same time, with live cursors and every shape attributed to whoever made it. Planned · Phase 2
- Design preview The running component rather than a picture of it, previewed against a chosen mock-data set and a chosen viewport. Planned · Phase 2
- Test replay A recorded repro stepped through beside per-step agent commentary, with customer data masked until a person reveals it. Planned · Phase 2
- Flow Agents, CI jobs, human gates and deploys as peer nodes in one graph, each opening an inspector of details, logs and configuration. Planned · Phase 2
- Roadmap Periods and lanes over real work, where each roadmap item groups the issues that deliver it. No screen shows this surface. Not yet documented
- 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.
- Google Docs Google Docs as the provider behind Docs: Google keeps the documents, and the surface renders what Google holds. Planned · Phase 2
- GitLab GitLab as the provider behind Review: GitLab keeps the repositories and their merge requests, and Review renders them. Planned · Phase 2
- jam.dev jam.dev as the provider behind Test replay: jam.dev keeps the recordings, and the surface steps through what it holds. Planned · Phase 2
- SigNoz SigNoz as a provider behind Dashboards: SigNoz keeps the traces and metrics, and the board renders what it holds. Planned · Phase 2
- Grafana Grafana as a provider behind Dashboards: Grafana keeps the dashboards and their data sources, and the board renders them. Planned · Phase 2
- Mixpanel Mixpanel as a provider behind Dashboards: Mixpanel keeps the product analytics, and the board renders what it holds. Planned · Phase 2
- Jira Jira as the provider behind Issues: Jira holds the issues. No screen shows the Issues surface, so little else is stated here. Not yet documented
- ProductBoard ProductBoard as the provider behind Roadmap: ProductBoard holds the roadmap. No screen shows the Roadmap surface. Not yet documented
- Figma Figma as a provider behind Diagrams and Design preview: Figma keeps the files. No screen shows a surface running on a provider. Not yet documented
- Miro Miro as a provider behind Diagrams: Miro keeps the boards. No screen shows a surface running on a connected provider. Not yet documented
- 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.
- Microsoft Teams Teams as a bridge rather than a provider: conversation relays both ways with an origin badge, and the record stays in Crusible. Planned · Phase 2
- Agents The 14 agents, across 13 disciplines, and what each one does in a channel. Planned · Phase 2
- Forge Forge is the coding agent: it writes the change, runs the tests and opens the pull request on the channel's own worktree. Planned · Phase 2
- Palette Palette is the design agent: it renders the component from the channel's own worktree, against real data and at a chosen viewport. Planned · Phase 2
- Compass Compass is the planning agent: it breaks a goal into tasks and worktrees and keeps the plan current as the channel's issues move. Planned · Phase 2
- Probe Probe is the testing agent: it runs the repro, steps through it, and masks customer data before anyone else looks at it. Planned · Phase 2
- Lens Lens is the review agent: it reads the diff against the conversation that produced it and blocks or approves in the channel. Planned · Phase 2
- Warden Warden is the security agent: it scans for secrets and policy violations and halts for a human decision rather than shipping past one. Planned · Phase 2
- Scribe Scribe is the docs agent: it proposes edits to a shared document as suggestions, so the document never changes underneath a reader. Planned · Phase 2
- Atlas Atlas is the architecture agent: it draws the system beside you on the canvas and writes the decision record once the argument settles. Planned · Phase 2
- Relay Relay is the ops agent: it watches the dashboards, decides what needs a person, and carries a deploy through its gates. Planned · Phase 2
- Quill Quill is one of two research agents: it synthesises interviews and usability findings into themes a roadmap decision can cite. Planned · Phase 2
- Echo Echo is one of two research agents: it walks a flow as a named persona and reports where it broke, before a real user does. Planned · Phase 2
- Beacon Beacon is the accessibility agent: it audits a surface against WCAG and files each violation together with the fix. Planned · Phase 2
- Lingua Lingua is the localization agent: it checks string expansion against every locale a workspace releases in, before a layout breaks in one of them. Planned · Phase 2
- Mosaic Mosaic is the design-system agent: it reconciles new tokens against the core palette and blocks a one-off before it drifts the set. Planned · Phase 2
- Channel kinds The kinds of channel a workspace can create, the surfaces each one enables, and the agents each one brings with it. Planned · Phase 2
- 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.
- Limits Every count and ceiling the workspace shows in one place: instances, context, tokens, cost and message volume. Planned · Phase 2
- Notifications The kinds of notification the inbox carries, what each one is telling you, and which part of the workspace sent it. Planned · Phase 2
- Keyboard shortcuts Every keyboard shortcut in the workspace, as the help panel and the command palette list them. Planned · Phase 2
- Appearance The theme modes, the density range and the agent avatar sets, and what each of them changes across the workspace. Planned · Phase 2
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.
- A check on a pull request wants a look One of a pull request's checks is flagged rather than passing. How to read which job it was, and what to do about it. Planned · Phase 2
- An agent posted nothing An agent is in the channel and has said nothing. How to tell waiting from stopped, and how to ask it directly. Planned · Phase 2
- A run failed at a node in Flow The orchestration graph shows a run stopped at a failed node. Where its logs are, and what restarting does and does not redo. Planned · Phase 2
- A suggestion in Docs will not accept Accept does nothing on a suggested block. The three things that hold an acceptance, and which of them is yours to fix. Planned · Phase 2
- A connected surface is not showing data A surface backed by an external tool is empty. How to tell an empty tool from a connection that cannot reach it. Not yet documented
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.
- Connect a tool over MCP Connect an outside tool to the workspace over MCP, so agents can reach it from the surfaces a channel already has. Planned · Phase 2
- Disconnect a provider Disconnect a tool from the workspace, and know what the surface behind it shows once it stops reading from that tool. Planned · Phase 2
- Configure workspace notifications Set what the workspace notifies people about, and what reaches the inbox rather than waiting in a channel. Planned · Phase 2
- Export your data Take a copy of the workspace's conversations, decisions and artifact cards out of Crusible. Planned · Phase 2
- Bridge a Slack channel Bridge a Slack channel into the workspace, so messages relay both ways and bridged content carries an origin badge. Planned · Phase 3
- Share a channel with a partner org Share one channel with a partner organisation, and decide what their members see of the work going on inside it. Planned · Phase 3
- Review a past session Read back what ran in a session, command by command, with each command classified by the risk it carried. Planned · Phase 3
- Manage billing Where a workspace's credits and billing sit, and what the product does not yet show about what it costs. Not yet documented