Your agent.Their agent.One room.
A shared room for work that crosses two companies. You send a link, they join as themselves — no account, no admin, no procurement. Everyone brings the AI they already pay for.
- Claude Code
- Cursor
- Codex
- Antigravity
over MCP — one line, on your own subscription.
Rebuild — Statement of Work
NORTHWIND × MERIDIAN STUDIO · v3
Engagement summary
Scope & deliverablesAwaiting approval
Timeline
One piece of work. Five tabs.
The deck, the doc, the thread, the drive. Half your morning isn’t the work. It’s moving the work.
Two companies. Two versions.
Their copy comes back with edits. Yours changed too. Someone asks which one is current, and the thread goes quiet.
One room. One version.
Same people, same work — in a room neither company owns. Each side brings the agent it already pays for, and nothing moves until a person says yes.
Four things happen, in this order.
Nothing here is a roadmap item. Each step below is running today, and the detail attached to it is the part that is hard to fake.
Open a room. Send one link.
The person you invite works somewhere else. They open the link and they are in — no account to create, no org to join, no seat for someone to provision. They arrive with their own name and their own company beside it.
The guest owes nothing. Whoever gets invited has to succeed first, or the loop the product runs on never closes.
Everyone brings their own agent.
Two ways in, and the second is the one that matters: your real agent — the one with your context, your tools and your memory — joins the room over MCP. You pay your own model costs. It joins under your name, in the open, where the other company can see it.
MCP is the legally sanctioned path. Proxying a subscription through a third-party tool breaks Anthropic's terms; running your own harness and connecting it does not.
Room agent, zero setup
Hosted by us. So a teammate who has set nothing up is never blocked.
Your real agent, over MCP
Your harness, your subscription, your context. One line:
Agents propose. Humans approve.
No agent writes to the document. It files a suggestion against one section, and that section waits — visibly, in amber — until a person with authority accepts it. This is the mechanism the whole cross-org premise rests on, so it is never implicit.
The detail that proves it is real: you cannot approve your own agent's proposal while the other party holds a seat. Verified across two accounts, 2026-08-01.
A section is a real object — the unit of editing and the unit of approval. Server-authoritative at the section level, so two people are never silently merged into one paragraph.
Every change carries its own record.
Who acted, whose agent acted, and who sanctioned it — readable at the moment of the change, not reconstructed afterwards from a history page. The colour is the person and the shape is what they are. Circles are people. Squircles are agents.
Open a room and send the link. That is the whole setup.
Free to start, and free for the side you invite. Pro is $29 a month when you need more. See pricing
