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

# 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.

<!-- https://crusible.dev/docs/guides/create-a-channel/ · doctype: how-to · role: member · reviewed: 2026-09-05 -->



1. <p>Select <strong>+</strong> beside <strong>Find a channel</strong>, at the top of the channel list.</p>
 (Result: The “New channel” dialog opens: templates on the left, a live preview of the channel on the right. The dialog says what it is asking for — “Pick a template — everything it sets up can change later”.)


1. <p>Select the template that matches the work in front of you. There are ten,
from Feature delivery to Customer support, and the preview on the right says
what each one sets up.</p>
 (Result: The right rail redraws for the template you selected. It lists the surfaces the channel opens with, the agents joining and their disciplines, and the workflow wired up — what each of them does first.)


1. <p>Read the right rail. It is the whole of what the template does. If the agents
are wrong for this work, select another template; changing it now costs
nothing.</p>
 (Result: The rail names the surfaces the channel opens with, the agents joining with their disciplines, and the first thing each agent does. Nothing has been created yet.)


1. <p>In <strong>Channel name</strong>, type a short name for the work. The field suggests the
shape: <code>feat-something-useful</code>.</p>
 (Result: The name is the work. It stays in the channel list and in the channel header from here on.)


1. <p>Select the <strong>Use</strong> button for that template — <strong>Use Feature delivery</strong>, for
example.</p>
 (Result: The channel opens under its group in the channel list, with the surface that template opens on the right and a starter card in the conversation saying what the channel is for and which agents are standing by.)


- **If this doesn't work:** <p>If no template matches, take the closest one. Everything it sets up changes
later in <strong>Channel settings</strong>: the members, the <strong>Access</strong> rows that govern what
agents may do on this work, and which surfaces the channel can open. If the
channel opens with agents you did not expect in the <strong>Direct to</strong> rail under
the composer, it came from a different template than you meant — open <strong>Channel
settings</strong> and change the members there. If <strong>+</strong> is not in the channel list at
all, the prerequisite above is the reason, and
<a href="/docs/troubleshooting/a-control-in-a-guide-is-not-visible/">A control in a guide is not visible</a>

says who to ask.</p>





You have a channel with a name, a state in its header, the surfaces this kind
of work needs, and the agents that do it already listening. Describe the work in
the composer and they start.

- [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.- [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.- [Channels are units of work](https://crusible.dev/docs/concepts/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.