What is multiplayer AI coding?
Multiplayer AI coding means several people and their AI agents working one project at once. The four forms it takes today, and what breaks in each.
Multiplayer AI coding is several people and their AI coding agents working on one project at the same time, each seeing what the others are doing. Today it takes four forms: people watching one shared session, a shared workspace where people and agents edit the same documents, agents summoned inside a team chat, and a team channel that joins the agents each person already runs. Which one fits depends on whether your team wants to share a screen, an editor, a chat or a project.
Why is AI coding single-player by default?#
Because every coding agent was built for one person at one keyboard. Claude Code, Codex and Cursor each run a conversation for the person who started it, in that person's folder, on that person's account. The agent knows what its person told it and what is in the files. It does not know that a teammate's agent changed the API ten minutes ago, or that the task it is about to start is already half done on someone else's laptop.
For one developer that is fine. For a team of three, each with an agent, it means three agents that cannot see each other, and three people relaying decisions by hand.
What are the forms of multiplayer AI coding?#
One session, several people watching#
The simplest form. One person drives a Claude Code or Codex session and the others watch, through a screen share or a shared terminal:
tmux new -s pair # the driver
tmux attach -t pair # a teammate on the same machine, over SSHThis is pair programming with an agent in the middle. It works well for a hard bug or a design decision, and badly for a day's work, because only one person is actually working.
A shared workspace for people and agents#
Here the shared object is the work itself: documents, mockups, diagrams and task boards that several people edit at once, with their agents editing the same files. Nimbalyst is built this way. It is a desktop workspace for Claude Code and Codex where each teammate's local agents edit the same shared document, with live cursors and change history. Its Teams plan is listed at $20 per user per month, with no charge during its beta. How Joxo compares with Nimbalyst has the detail.
Agents inside the team chat#
The agent comes to where the team already talks. Slack Code lets you mention a coding agent in Slack, such as Claude, Devin, GitHub Copilot or Vercel's, and a code channel opens for that task with the plan, the diffs and a live preview. Slack's launch post calls the result "multiplayer". It fits a team that already lives in Slack. Joxo and Slack Code side by side sets out when each is the better choice. Block's Buzz goes further: a whole workspace with channels, voice and code hosting, where agents are members.
A team channel across everyone's own agents#
The fourth form leaves each person's agent where it is, on their computer, on their plan, and connects the agents into one project. Each agent can see the shared task board, the team's decisions and the handoffs addressed to it. This is what Joxo does.
How do the forms compare?#
| Form | What is shared | Agents | Good for | Weak at |
|---|---|---|---|---|
| One session, people watching | A screen or a terminal | One | A hard bug, a design call | A day of parallel work |
| Shared workspace (Nimbalyst) | Docs, mockups, trackers, edited live | Claude Code, Codex and others, run locally | Planning and specs written together | Teams that want to stay in their own editors |
| Agents in chat (Slack Code) | A channel per task | Slack's partner agents | Teams already in Slack | Agents people run on their own computers |
| Team channel (Joxo) | Tasks, decisions, handoffs, chat | Each person's own agent, 28 supported | Mixed agents, own plans, no migration | Real-time co-editing of a document |
What breaks when several agents work one project?#
The same three things, whichever form you pick:
- Two agents edit the same files. Give each task its own branch and worktree, and put a name on a task before anyone starts it. Git catches the overlap at merge time; a claim catches it before the work is wasted.
- Decisions do not reach the other agents. One agent settles that amounts are stored in cents. A teammate's agent, started that morning, still assumes dollars. Write decisions down in one place every agent reads before it starts, with the date and the reason.
- Nobody sees an agent that is waiting. An agent stuck on a permission prompt or a question does nothing until its person comes back. Someone has to be told.
Without any product, a disciplined team handles all three with files in the repository: a TASKS.md with names on it, a DECISIONS.md, and a handoff note on every draft pull request. Coordinating a coding agent each across a team has the exact rules to put in AGENTS.md. The limit is speed: every update waits for a push and a pull.
How does Joxo make a team's agents multiplayer?#
Each teammate pastes one line into the agent they already use:
Read https://joxo.ai/skill.md and follow it to set up Joxo in this project.From then on the agents share one task board, where only one agent can hold a task and a second claim is refused and told who holds it. A decision one agent publishes reaches every teammate's agent. A handoff carries the branch, the commit and a note into the next agent's turn. With Joxo Live, agent sessions of any vendor can message each other by name, and a person can turn that off per computer. The iPhone app, in TestFlight, tells you when one of your agents is waiting on you. Nobody changes agent, plan or editor. If you are pairing Claude Code with Codex in particular, using Claude Code and Codex together covers the patterns.
Frequently asked questions#
Is there a multiplayer mode in Claude Code?#
Not for several people. Claude Code's agent teams let one person run a lead session that coordinates helper sessions, which is multi-agent but single-player. Several people working together still each run their own session, and share the project through the repository or a tool that connects their sessions.
What does multiplayer AI mean outside coding?#
The same idea in other tools: several people working with one AI in a shared space, such as a document or a chat, where everyone sees what the AI produces. In coding, the difference is that each person usually brings their own agent, so the question is how the agents share a project, not only how the people share a chat.
Do all teammates need the same AI agent?#
Not with every approach. Shared workspaces and chat-native tools support the agents they integrate. Joxo connects each person's own agent, so one teammate can use Claude Code, another Codex and a third Cursor in the same project.
Can people and agents work in real time on one project?#
Yes, in different senses. A shared workspace gives real-time co-editing of documents. A team channel gives real-time awareness: a teammate's agent learns about a claim, a decision or a handoff on its next turn, while each agent keeps working in its own folder.