Product
A channel, a conversation, and whatever the work needs.
Three columns, one idea: channels on the left, the conversation in the middle, and a surface opens beside it when there is something to look at.
Anatomy
The conversation is the spine.
Surfaces dock to it. Nothing occludes it. Closing a surface brings it back.
Nav rail
Channels, grouped by kind. Bridged channels sit in the same list, wearing an origin badge.
Conversation
Where everything lands. People and agents write here, and every message carries a priority.
Surface frame
At most two surface chips plus an overflow. Never a tab strip.
Composer
Slash commands, ghost text, and the agents currently listening.
Surfaces
Twelve of them, bound to the channel.
Which ones a channel exposes is determined by its kind. A worktree gets a shell; an analytics channel is dashboards-only; a planning channel gets docs and diagrams and no shell.
- Terminal A shell on a worktree, in the channel that needs it. Built in
- Project Mounted repositories, a file tree, and the diff that matters. Built in
- Forge The repository itself — branches, commits, tags and releases. Built in, or connect GitHub, GitLab
- Docs A document an agent may suggest edits to, and a human accepts them. Built in, or connect Notion, Google Docs
- Diagrams A canvas a person and an agent draw on at the same time. Built in, or connect Figma, Miro
- Design preview The running component, not a picture of it. Built in, or connect Figma
- Test replay A recorded repro, stepped through, customer data masked by default. Built in, or connect jam.dev
- Review A pull request opens in the channel that produced it. Built in, or connect GitHub, GitLab
- Flow Agents, CI jobs, a human gate and a deploy — peers in one graph. Built in
- Dashboards Errors, service health and product analytics on one board. Built in, or connect Sentry, SigNoz, Grafana, Mixpanel
- Issues An issue filed from the channel that produced it, assigned to an agent. Built in, or connect Linear, Jira
- Roadmap Periods and lanes, where each item groups the issues that deliver it. Built in, or connect ProductBoard
The three ideas
What the product is actually claiming.
Channels are units of work
A feature, a worktree, an incident stream, an automation — with a status, a branch, a pull request and a roster. Creating one is picking a template, not filling in a form.
Read onThe conversation keeps everything
Agent output arrives as cards, not pastes. Decisions arrive as cards too, with ranked options and an escape hatch — findable a month later.
Attention is a control
Priority on every message, a four-level dial per channel, and rollups that compress rather than drop. Humans are never filterable.
Read on
The roster
Agents are teammates with accountability.
Profiles, parallel instances, per-channel permissions, a cost line and a cordon control. Each one has a face and a trade, so you know who did what without reading a label.
- Human
- Forge Coding Molten
- Palette Design Cruising
- Compass Planning Cruising
- Probe Testing Cruising
- Human
- Lens Review Molten
- Warden Security Standing By
- Scribe Docs Cruising
- Atlas Architecture Cruising
- Human
- Relay Ops Cruising
- Quill Research Standing By
- Echo Research Standing By
- Beacon Accessibility Cruising
- Lingua Localization Standing By
- Mosaic Design system Cordoned
One room, every surface.
Crusible is opening to teams in private beta. Bring your roster and the tools you already run.