See the complete route index at https://crusible.dev/llms.txt before following links.

# 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](https://crusible.dev/docs/guides/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](https://crusible.dev/docs/guides/change-a-channels-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.
- [Use the task board](https://crusible.dev/docs/guides/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.
- [Go solo](https://crusible.dev/docs/guides/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](https://crusible.dev/docs/guides/archive-a-channel/) — Close a channel whose work has shipped, and keep its conversation, its decisions and its artifacts readable afterwards.
- [Set the signal dial](https://crusible.dev/docs/guides/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](https://crusible.dev/docs/guides/mute-one-agent/) — Quiet a single agent in one channel from the volume controls, without changing the level the channel shows you.
- [Read rollups and digests](https://crusible.dev/docs/guides/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.
- [Work the inbox](https://crusible.dev/docs/guides/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.
- [Direct a message to one agent](https://crusible.dev/docs/guides/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](https://crusible.dev/docs/guides/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](https://crusible.dev/docs/guides/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](https://crusible.dev/docs/guides/check-an-agents-cost-and-context/) — Read an agent's profile: its running instances, their context meters, and the uptime, tokens and cost it has run up.
- [Cordon an agent](https://crusible.dev/docs/guides/cordon-an-agent/) — Stop new work routing to an agent while it finishes what it is already holding, and lift the cordon afterwards.
- [Set agent permissions in a channel](https://crusible.dev/docs/guides/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.
- [Review a pull request](https://crusible.dev/docs/guides/review-a-pr/) — 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](https://crusible.dev/docs/guides/replay-a-test/) — Step through a captured run beside its replay, read the agent's commentary on each step, and reveal masked data when you must.
- [Trace a run in Flow](https://crusible.dev/docs/guides/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.
- [Replay a session](https://crusible.dev/docs/guides/replay-a-session/) — Scrub through a past terminal session command by command, and read what each command did and how risky it was.
- [Have an agent operate a connected tool](https://crusible.dev/docs/guides/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](https://crusible.dev/docs/guides/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.
- [See which provider a surface is using](https://crusible.dev/docs/guides/see-which-provider-a-surface-is-using/) — Find out which tool holds the data behind a surface, and who in your workspace connected it.
- [Bring existing work in](https://crusible.dev/docs/guides/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.
- [Work in a bridged channel](https://crusible.dev/docs/guides/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.
- [Work with a partner org](https://crusible.dev/docs/guides/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.