Select + beside Find a channel, at the top of the channel list.
(Result: The “New channel” dialog opens, with “Feature delivery” selected and a live preview of the channel on the right.) 1.Keep Feature delivery selected. In Channel name, type a short name for
the change. The field suggests the shape: feat-something-useful.
Select Use Feature delivery.
(Result: The channel opens under “Features” in the channel list. Its conversation shows one starter card, “Describe the feature to get moving”, and the Project surface is open on the right.) 1.Type what you want changed into the composer and send it. Say what is different when the change is done, not how to do it. The agents work out the how.
(Result: Compass answers with an artifact card, “Delivery plan”, that counts the tasks and carries an “Open plan” link. Your message and the plan are the first two entries in the conversation.) 1.Wait, and read along. Forge takes the first task on a fresh branch, and Probe tests what Forge commits. Both work in the open, and their work arrives in the conversation as artifact cards rather than pasted output. The dialog promised a pull request as soon as the first commit lands, and that is what Forge opens.
(Result: Forge posts a diff card: the files it touched, the lines added and removed, and “Open in Project”. Probe posts a test-run card: passed, failed and duration, and “Open in Test”. While they work, the channel header reads “Cruising” with a count of what is running; once Forge's pull request opens, it reads “In review”.) 1.Wait for the pending-decision card, then read its options and select one. The preview promised this gate before you created the channel — “Lens blocks the merge until a human approves” — and the card is how an agent asks: headed Needs a human, carrying a question, ranking its options with the first marked Recommended, and offering a last row that opens a conversation with the agent instead. The agent pauses until you answer.
(Result: Your choice lands in the conversation as a message tagged “Decision”, and the agent that asked carries on.) 1.Select Docs in the channel header.
(Result: The Docs surface replaces Project. The doc's header shows a pill counting the agent suggestions waiting on it, and “Contributors” lists every person and agent who has written in it.) 1.Select the suggestions pill in the doc’s header. Each suggested block shows inline beside the text, marked with the agent that wrote it. Press Accept on the one you want to keep.
(Result: The block joins the doc, credited to the agent that wrote it. Until you pressed “Accept”, the doc read exactly as it did before. A suggestion never changes a doc on its own.) 1.Select the three-dot button at the right of the channel header. It opens Switch surface; select Review.
(Result: The Review surface replaces the one that was open, headed “Pull request, checks and comments”. Forge's pull request, its checks and its comments are read here.) - **If this doesn't work:**Nothing happened after a step? Agents post when they have something to show,
and the channel header reads Cruising while they work — so give them a few
minutes, then act. No pending-decision card yet means no agent needs you yet,
and no suggestions pill on the doc means Scribe has drafted nothing for it so
far; both arrive on the agents’ clock, so carry on and come back to the step
when they do. Ask the agent directly: type @forge in the composer, pick it
from the Mention list, and ask what it is waiting on; it answers in the
channel. Look at the Direct to rail under the composer: if Forge and Probe
are not in it, the channel was made from another template, so select + and
make one from Feature delivery. Select Inbox at the bottom of the
channel list: a Blocked or Needs a look entry there names what stopped
and why, and
A channel shows Blocked
reads
that entry with you. Planned.
A page for an agent that posts nothing at all is planned.
If a step still does not match this page, the rest of Troubleshooting is written for that moment, and anyone in your workspace can read the channel you are in, so asking a colleague costs you nothing.
You have a channel with a plan, a branch with commits on it, a test run, a doc with a block you approved, and a pull request that Lens holds until a human approves it. That approval is the last gate, and it belongs to a person. An agent never merges without a human unless an admin turns that on in the channel's settings. That is your first melt. - [Guides](https://crusible.dev/docs/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.- [Concepts](https://crusible.dev/docs/concepts/) — What a channel is, who holds the record, and how a surface answers to the conversation that opened it.