Understand multiplayer AI
Most agents are single player: one person, one chat, one agent, results shared after the fact. Multiplayer AI is agents, context, memory and permissions that belong to a team. In NLW's words, it is the move from private outputs to visible work, from personal memory to shared context, from individual leverage to team capability.
The AI Daily Brief episode that lays out the rationale for this sprint: why agents built for one person stall, and what changes when a team shares one. Watch or listen now, or come back to it any time.
Episode page →| Level | What is shared | What stays private | Where you see it |
|---|---|---|---|
| Shared brain | The identity and context files every person's own agent reads | Every conversation. Only what agents write back is shared | A shared folder, a chat project |
| Shared agent | One agent with its own accounts and memory that everyone uses | Depends on the tool; decide it before the first task | Claude Tag, ChatGPT workspace agents, Copilot Studio, Notion agents, OpenClaw |
| Shared session | One live conversation everyone is in | Nothing inside the session | OpenClaw 2.0 multi-user, Slack Code |
Level 1 is enough for most teams' first sprint. Levels 2 and 3 need an owner.
- 1. What does it know? The team context, kept in one place and dated.
- 2. Who is in charge? One owner. Anyone can hand the agent work; the owner sets its priorities and settles contradicting instructions. Think of a shared intern: everyone can ask, one manager decides.
- 3. Whose accounts does it use? On behalf of whoever is asking, its own governed identity, or one shared login. The last one only for read-only, non-sensitive sources.
- 4. Where does it remember, and who can see the conversations? Private per person, the channel, or the live session. It differs by tool.
- 5. How fast does it earn autonomy? Read-only and drafts first. Widen after two people have checked its work for a few days.
| Tool | Who sees the conversations |
|---|---|
| Shared folder agent | only you |
| ChatGPT workspace agent, Copilot Studio agent | only you |
| Notion custom agent | anyone with Full Access sees every run |
| Claude Tag, Slack agents, NanoClaw | everyone in the channel |
| OpenClaw 2.0 multi-user, Slack Code | everyone in the session |
Visible is a feature for transparency and a surprise for whoever assumed privacy. Say which one you chose before the first real task.
Rung 1. A shared folder your own agents read
Pick this if your team uses different AI tools, or IT allows nothing new. It is enough for most teams' first sprint.
Rung 2. A shared agent in the tool your team already lives in
Pick this if the whole team is on one suite and an admin can flip a switch this week.
Rung 3. A shared agent on a hosted harness
Pick this if your suite has no shared-agent feature, or you want more control than a suite agent gives, and someone on the team is comfortable with settings pages or a small monthly bill.
Rung 4. A shared live session
Pick this only for genuinely simultaneous work: co-building, incident response, live analysis. Most teams should not start here.
Full options and setup steps in Week 4 →
- Fleets of personal AIsEveryone has an agent, nobody shares one. Start with one shared use case.
- Context driftFive versions of the company description, maintained by nobody. One dated repository, one owner, a weekly prune.
- Too many cooksSeveral people give the agent contradicting instructions. One owner settles them; standing instructions live in the repository only.
- Shared-login leakageThe agent shows one person's inbox to the team. Its own identity or per-user access; never a shared login for write or restricted access.
- The DM trapAn agent in a channel with no turn-taking and no owner. Reply only when tagged, one owner per session.
- Only the owner used itThe agent sat inside one person's work, so it was never multiplayer. Say so in the verdict and move to the next candidate.
- Unowned agentAbandoned within a week. A named owner and a retirement review.
- Colliding write-backsTwo agents write the same shared file. One merger, or put the folder in version control.
You will keep personal agents where taste and control matter: your own writing voice, your own assistant. Shared agents are for the work that lives between you. A shared agent can spawn personal sub-agents for individual steps. Most teams end up with both.