The bottleneck becomes the person running the agent. They have to relay context in, copy results out, explain what happened, and keep everyone else updated.
People are already using agents heavily, especially for coding. Most of it is still single-player: one person, one thread.
No Digg Deeper questions have been answered for this story yet.
Useful agent work should attach to the task, doc, or project where the work is already being discussed.
Teammates should be able to follow along, comment, review output, see changes, and understand permissions.
The bottleneck becomes the person running the agent. They have to relay context in, copy results out, explain what happened, and keep everyone else updated.
Coding agents make this especially obvious. Internally, we have an agent called Boxy with access to our codebase, services, secrets, tests, CI, and deploy paths.
External agents let Boxy run in our own infrastructure, while the collaboration happens on the Notion task.