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.
The guides are grouped by the job you are on: Run a channel, Tune your attention, Work with agents, Review and ship, Work with connected tools, and Bridged and external.
Run a channel
- 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
Tune your attention
- 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
Work with agents
- 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 and ship
- 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
Work with connected tools
- 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
Bridged and external
- 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