
Sep 7, 2026 · 26 min
Teams move AI agents from private tools to shared work
The Multiplayer AI Sprint: Build Your Team’s First Shared Agent
The next productivity gains may depend less on individual prompting than on giving teams shared context, visibility, and control over agentic work.
- 1Multiplayer AI makes agent work visible, steerable, and reusable across a team rather than trapping it in private sessions.
- 2The four-part sprint helps teams inventory current AI use, build shared context, map workflows, and test one agent on real work.
- 3Shared agents could reshape software development and extend into sales, support, legal work, analysis, and marketing.
Don't miss
Nathaniel turns the multiplayer-AI thesis into a concrete four-week sprint that ends with two teammates testing one shared agent on real work.
The brief
AI agents have transformed individual work, but much knowledge work depends on coordination; the episode argues that shared team contexts are the next frontier.
Multiplayer AI means agents expose their work, accept live direction, support handoffs, and preserve durable organizational knowledge instead of producing private outputs.
Examples include Claude Tag in Slack, Every’s internal experiments, and OpenClaw’s shared sessions, where developers can inspect, redirect, and continue agent work.
The idea extends beyond coding into sales, support, legal work, analysis, and marketing, with Y Combinator’s interest signaling a broader product category.
The four-part Multiplayer AI Sprint guides teams from an inventory of current AI use to shared context, workflow mapping, and a real-world agent test.
The practical test is simple: deploy one shared agent on real work, have at least two people use it, and judge whether the workflow improves.
What was said on this episode
27 statements · 24 positive · 1 negative · 1 mixed · 1 neutral
Leading AI-using teams will shift from individual to multiplayer AI.
“the best, most dynamic AI-using teams are going to shift from single-player AI to multiplayer AI”
Listen at 0:31
Managing extensive agent teams will become part of effective knowledge work.
“the fact that all of us now gets to be a manager of a big extensive team of agents that themselves can spawn subagents to do lots of different work is now just part and parcel of being an effective knowledge worker”
Listen at 4:59
Meaningful knowledge work will increasingly occur through collaboration with other people.
“much of the meaningful work that we do will not be in our own individual silos, but at the intersection of where we work with other people”
Listen at 5:13
Agent design will move from individual silos into shared team spaces.
“the next frontier of agent design is going to move agents from the individual silos in which they have operated so far to the shared spaces that teams inhabit together”
Listen at 5:23
Agents will become reusable infrastructure for organizations.
“agents as reusable organizational infrastructure”
Listen at 6:52
Claude Tag provides team-shared Claude instances.
“Claude Tags are instances of Claude that are shared across an entire team”
Listen at 8:03
A shared Claude can accumulate context from its team channel over time.
“Because Claude is multiplayer, it can also learn over time.”
Listen at 8:52
Shared Claude reduces repeated explanations by retaining team-channel context.
“Because it is operating in that shared team multiplayer space, each individual user that comes in and needs something doesn't have to explain things over and over again from scratch.”
Listen at 9:00
Shared agent sessions enable teammates to inspect, steer, and take over ongoing work.
“The session stops being a private conversation between one developer and a model. It becomes a shared piece of work another trusted developer can inspect, steer, or take over.”
Listen at 11:14
OpenClaw’s shared session lets trusted developers inspect, steer, or take over work.
“It becomes a shared piece of work another trusted developer can inspect, steer, or take over.”
Listen at 11:18
Multiplayer AI will extend beyond software coding.
“And I don't believe that this is just going to be constrained to coding.”
Listen at 14:31
Multiplayer AI will extend beyond software coding.
“I don't believe that this is just going to be constrained to coding.”
Listen at 14:31
AI agents are powerful team tools that are still predominantly used individually.
“AI agents are the most powerful new tool a team has, but it's the one thing people still use by themselves.”
Listen at 15:21
AI collaboration will shift away from read-only, private transcripts.
“That's about to change.”
Listen at 15:41
AI agents can increasingly run tasks lasting hours, days, or weeks.
“Agents are starting to run tasks that take hours, days, even weeks.”
Listen at 15:43
Teams should share multiplayer agents wherever they jointly work on a problem.
“Anywhere a team already crowds around one problem, there should be multiplayer agents they all share.”
Listen at 16:17
Teams should prepare early because multiplayer AI is coming.
“All I care about is you getting ahead of everyone else by understanding that multiplayer AI is coming and getting there first.”
Listen at 19:06
Overlapping team work is a candidate for shared-agent deployment.
“When you have work that overlaps with others, that becomes a candidate for where a shared agent could live.”
Listen at 21:38
Teams should score shared-agent candidates across four dimensions and prioritize highest-scoring options.
“A simple way to figure out where you want to start experimenting would be to score each of those axes on a 1 to 5 scale and then squint at the ones with the highest scores as your potential candidates.”
Listen at 22:12
Teams should test one context-loaded shared agent with at least two members on real work.
“The idea is to ship and start to use one shared agent on whatever tools you already have access to, loaded with your team context, used by at least 2 of you on real work.”
Listen at 22:27
Teams should experimentally test shared agents and evaluate whether they improve work.
“The goal then is to test one shared agent, give it some amount of time to see if and how it changes the work, and then ask if it actually improved things.”
Listen at 22:46
Some overlapping team workflows may currently provide little value from agents.
“It may be that some use cases, despite there being a lot of shared overlap between you and others, just aren't the right shape for an agent to get a lot of value currently.”
Listen at 22:55
Listeners lacking AI foundations should review the free AgentOS program.
“I would recommend either A, going back through some of our free programs like the AIDB AgentOS program”
Listen at 23:51
The Agent Leadership Program will place participants among the top 1% in agent understanding.
“the Agent Leadership Program is going to leave you in the top 1% of people who actually understand how to build and interact with agents”
Listen at 24:07
The future direction of AI work is toward multiplayer agents.
“it seems fairly obvious to me when I squint at it that this is the direction things are headed”
Listen at 24:28
Knowledge workers will probably manage fleets and teams of individual agents.
“you will probably have entire fleets and teams that you manage”
Listen at 24:39
Completing the sprint will better prepare teams to use emerging multiplayer AI tools.
“if you and your team work your way through this sprint, you will be in a significantly better position to use these new multiplayer AI tools as they come online”
Listen at 24:55
Statements are attributed to the speaker as said on the episode and reflect their view at the time, not PodLume's. They are not advice.
Weekly email
State of the Pod, every Monday
The week's most-discussed names and stories from podcasts, with the moments behind them. Free, five minutes, unsubscribe in one click.