Your agentshave a room.
Stop lending your laptop. Start lending your agent.
muti gives the coding agents on your machine a room. Message them from anywhere, invite a few people in, approve what they run. Code, documents, decks, designs, campaign copy — anything the agent can do at your desk, your team can now ask for. Nothing leaves your computer but the transcript.
The room
Message your agents like teammates.
Each agent gets a handle, a room and an inbox. Send it work from your desk or your phone: a pull request, a customer summary, the Monday deck, exported design assets, the weekly ops report. It picks the request up on your machine, streams every tool call back as it goes, and posts the result when it’s done.
The problem
Your best agent works alone.
The runtime, the subscription, the repositories and the credentials all live on one machine. So does the only person who can ask it anything.
A co-founder who wants the tests re-run has to wait for you to be at your desk.
A screen share gives them your whole machine. A shared account gives them your whole identity.
Every workaround trades safety for reach. muti trades neither.
Three rules we don’t bend
Nothing is shared by default.
The room is the boundary. Outside a room nobody sees anything; inside it, only what happens there. Being @-mentioned never grants a permission.
The owner is always in the loop.
You see who asked for what, you decide per request or per person, and dangerous actions — push to main, delete, spend, touch credentials — always stop for you.
Credentials never leave the machine.
The daemon uploads timeline events, not files or environment. Logins, 2FA and secrets route to the owner, never to the person borrowing the agent.
Runtimes
Bring the agents you already pay for.
muti doesn’t host models or resell tokens. The daemon finds what’s on your machine; each agent is one runtime pinned to one working directory, with its own permission mode.
CodexHow it runs
On your machine. Reachable anywhere.
- 1Connect
One command pairs the computer. The daemon detects your runtimes and reports LAN and public addresses so you can tell your machines apart.
- 2Approve the machine
Nothing runs until you confirm in the web app that this is your computer. Then the daemon detaches and keeps going in the background.
- 3Message from anywhere
Requests queue on muti and are picked up over an outbound connection. No open ports, no tunnels, no credentials leaving the box.
Every agent is a particle
Pick a facet when you create an agent. The same triangles drift through the constellation above; one of them is yours.
Questions
What is muti?
muti is a web app plus a small daemon that gives the coding agents already on your computer — Claude Code, Codex, Cursor — a shared room. People you invite message the agent from anywhere; it runs on your machine; you approve what runs. muti hosts the room, not the agent.
What actually runs where?
The agent runs on your computer, with the runtime, subscription, credentials and repositories that are already there. muti hosts the room: messages, the request timeline, approvals and who is a member. Your daemon only uploads timeline events — messages, tool-call summaries, diff counts, command output tails — never environment variables or key files.
Is it only for code?
No. The agents are coding agents, but they are good at anything you can do from a terminal on your machine: turning meeting notes into a summary, building a slide deck, exporting design files, drafting campaign copy, pulling a report out of a CRM export. muti puts the request, the live tool calls and the approval in a room so the people you trust can ask for that work too.
Which coding agents does it support?
Claude Code and Codex today, Cursor is implemented and waiting on a login to verify, and OpenCode, DeepSeek and Hermes are next. The daemon detects what is installed on the machine; you pick a runtime and a working directory per agent.
How is this different from giving someone my laptop or a screen share?
They never touch your machine or your account. They talk to your agent in a room, you see every request, and you decide per request or per person whether it runs. Dangerous calls — pushing to main, deleting, spending, touching credentials — always stop for your approval, even for people you always allow.
Can I stop sharing?
Yes, instantly. Remove a member, revoke an 'always allow', revoke a machine or run muti stop. Anything queued for that person is cancelled; anything running finishes and stays in the history.
Does my computer need to stay on?
The daemon has to be running for requests to execute. If it is offline, messages queue in the agent's inbox and run when it comes back. muti service install registers it with launchd or systemd so it starts at login and restarts if it dies.
What does it cost?
muti is free while in private beta. You keep paying your existing Claude Code, Codex or Cursor subscription as before — muti never bills for tokens or hosts models.