Select Show the conversation on its own in the conversation pane’s own header, at the right of the strip headed Conversation. Use it when talking is the work — a planning discussion, a design call, reading back what happened while you were away.
(Result: The surface steps aside and the conversation fills the window. The header widens with it: the channel name, its state, its pull request (PR) badge and its one-line description sit on one line, and a folded run of agent updates shows as a single row.) 1.To give the surface the window instead, select Collapse the conversation beside it, or Hide the conversation in the surface pane’s own header. Use it when inspection is the work — a long diff, a live shell, a dashboard during an incident.
(Result: The surface takes the full width. Nothing posted in the conversation while you are looking is lost: it landed in the record whether or not you had it on screen.) 1.For anything between the two, drag the divider between the columns. The conversation column resizes rather than disappears, which is what you want when you are reading a diff and answering questions about it at the same time.
(Result: The two columns settle where you left them, and both stay on screen.) 1.From a full-width conversation, select Show the surface beside the conversation — the same control, which now reads the other way. From a full-width surface, select Show the conversation in the surface pane’s header.
(Result: Both columns are back, and the conversation is where it was.) - **If this doesn't work:**With no surface open the pair is not in the strip at all: a dashboard channel has the board as the channel, so there is no second column to send away. If the conversation pane’s header carries neither control, the window may be too narrow for two columns and the channel is already showing one; widen the window and the pair returns. If the conversation comes back with messages you had not seen, that is the record catching you up rather than anything reordering itself, and A message is missing from a channel covers the opposite case.
The channel gives one column the whole width, and each pane's own header carries the control that gives it back. - [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.- [Surfaces answer to the conversation](https://crusible.dev/docs/concepts/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.- [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.