Your people already work with Claude and Cursor, one person at a time. A room makes those sessions multiplayer, inside the Slack you already use, on top of the subscriptions you already pay for.
Every team rolling this out hits the same three walls. Everything below answers them, in order.
Four people on one problem open four sessions. The context the first one built over two days lives in their window and nowhere else, so the next three walk the same dead end. The best any tool offers is a link to a transcript: you can read it, you cannot continue it.
Answered by one thread, in Slack
It asks which service, what changed and who owns it, because it never saw the migration that shipped last quarter or the approach a huddle ruled out in March. You end up pasting your own company into the prompt, every time.
Answered by your Company Brain
It hands you a command and you go and run it yourself. Anything that touches a real system comes back to a person, which is also the reason nobody trusts it to touch one.
Answered by the console
There is no new tool to adopt. You invite Caliber to a channel, and the channel becomes a room: your people, as many agents as it needs, one thread.
One change to how the work happens, and one to what the agent already knows before it starts.
The session stops belonging to one person. Whoever joins at noon scrolls up instead of starting over, and what the agent worked out at nine is still there to build on.
A plain room asks which service and who owns it. A room on your Company Brain already knows, because it reads your commits, tickets, meetings and the sessions your people ran alone.
A shared chat is a room. A shared chat that knows your company is a war room.
Slack is where the work happens. This is where you decide what a room may reach and what it may do. That is what lets an agent run things instead of suggesting them.
Every room carries a posture you set: read only, act as the person asking, or stop for approval. It inherits the permissions that person already has, executes in your own cloud, and writes what it learned back to the brain.
The multiplayer harness Y Combinator open-sourced under MIT. Model agnostic, so you are not tied to one vendor.
Your models, your cloud, your permissions. Raw data never leaves your systems.
qm is young and moving fast. We absorb the churn, so your platform engineer stays on your product.
Not org wide on day one: one channel, one live investigation. Bring us the problem currently eating four people in parallel.
