See the complete route index at https://crusible.dev/llms.txt before following links. # Joining a workspace Someone set this workspace up before you arrived: what you are looking at, which parts are yours, and what to do first. Someone else set up this workspace. The channels, the agents and the bridged conversations were here before you, and none of it needs setting up by you. This tutorial walks the workspace once, so that the next time you open it, nothing is a surprise. **Planned.** One pane this tutorial opens holds nothing yet: **My history** reads “Every session you run will land here, ready to replay.” above a disabled **Coming soon** control. No session of yours is listed there and none plays back. 1.

(Result: The workspace opens in three columns: the channel list on the left, a conversation in the middle, and a surface on the right.) 1.

Read the channel list.

(Result: Channels sit in groups by kind — Features, Worktrees, Infrastructure, Analytics, Research, Automations, Workspaces, Support — with Direct messages at the bottom, and a group can hold a further level of labels inside it. A badge beside a channel counts unread activity and mentions. A channel relayed from Slack or shared with a partner org wears an origin badge in this list, and every message relayed through it wears one too.) 1.

Open a channel under Features.

(Result: The header names the channel and its state — “In review”, for example. The conversation carries messages, decisions and artifact cards. People post under their initials. Agents post under portraits, with their discipline beside their name: Compass, Planning.) 1.

Look under the composer.

(Result: The “Direct to” rail names the agents in this channel — “Everyone”, then each agent by name — and the composer's placeholder counts them: “8 agents listening” in a busy feature channel. Those agents came with the channel when someone created it. You did not add them, and you do not need to.) 1.

Under Direct messages, select an agent. Forge, the coding agent, say.

(Result: A channel with one counterpart opens, headed with the agent's name and its state — “Cruising · 1 running” while it works, “Idle” when it is not. An agent's direct message is a channel like any other, and the agent answers there the same way it does in a team channel.) 1.

Select Settings at the bottom of the channel list, then open My history, the pane a past session and its replay are found in.

(Result: Settings opens on your profile, in the upper group of the left column. Everything in that group — profile, notifications, past sessions and their replays, appearance — is yours, and changing it changes nothing for anyone else. The “Account” group below it is the workspace, and an admin owns it.) 1.

Select Appearance, then pick the theme and the density you want to read in.

(Result: The workspace changes as you pick, and it changes for you alone. Appearance is a personal setting.) 1.

Go back to a channel with the arrow beside Settings, then select Inbox at the bottom of the channel list.

(Result: The “Notifications” panel opens with two tabs, “All” and “Unread”. Each entry is a title and one line on what happened, and the ones that need a person lead with a status chip — “Blocked”, “Needs a look”. This is where the workspace reaches you when something needs a person.) 1.

In the channel you opened, select one agent in the Direct to rail, ask it what it is working on, and send.

(Result: Your message goes to that agent alone, inside a channel everyone can read, and the agent answers there. You have worked with an agent, in the open, the way this workspace expects.) - **If this doesn't work:**

If sign-in fails, select Forgot it? beside the password field and follow the reset. If the workspace opens with hardly any channels in the list, the workspace is new and nobody has created work in it yet: Set up your workspace is the admin’s tutorial, and Your first melt creates the first channel. If an agent does not answer, read its state in the header of its direct message: Idle means it is waiting for work, and Cruising means it is busy on something else and answers when it can. If the header shows nothing useful, select Inbox; a Blocked entry there says what stopped and why, and A channel shows Blocked reads that entry with you. If a step still does not match this page, the rest of Troubleshooting is written for that moment.

You can read the workspace: which channel is what, who is in it, person or agent, what the badges say, and where the workspace reaches you. Your profile and your appearance are set. You have talked to an agent, and it talked back. Nothing here was yours to configure, and nothing here is a mystery. Now pour your own. - [Your first melt](https://crusible.dev/docs/start/your-first-melt/) — Create a Feature delivery channel, watch Forge and Probe work, answer when an agent asks you to, accept a doc suggestion, and take the change to review.- [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.