Shared control of AI agents: the driver model
In a shared session, each agent has one driver at a time: the person whose instructions it follows. Everyone else can watch, suggest or ask to take over. One driver keeps an agent from getting two sets of orders.
Why one driver?
If two people prompt an agent at once, it gets mixed instructions. A single driver keeps its direction clear, and the rest of the team still takes part.
What can everyone else do?
- Watch every step.
- Suggest a redirect. It lands at the agent’s next step.
- Request control.
- Interrupt, where the session allows it.
The session owner can always pause or cancel a run.
How does control change hands?
Control can pass from one person to another. The agent keeps its context, and the log records who was driving.
Each agent has its own driver, so one person can steer one agent while a teammate steers another.
Where does this fit?
This is how a shared session works, and a core part of multiplayer AI. It also maps onto pair programming, with the driver and navigator roles.
Common questions
Can different people drive different agents?
Yes. Each agent has its own driver.
Who can pause an agent?
The session owner, at any time, even when someone else is driving.
Does the agent lose context when control changes?
No. The agent keeps its context, and the session log records who was driving.