Multiplayer agentic engineering — Arjun Singh, Superconductor
The talk outlines 'multiplayer agentic engineering,' focusing on how human teams and AI agents can collaborate effectively across diverse systems. Key recommendations include making workflows model-agnostic, integrating agents into every human interface (Slack, GitHub), ensuring work visibility via artifacts, and treating all external signals (emails, meetings) as code inputs. Crucially, the speaker emphasizes that these advanced agentic workflows must operate within isolated cloud environments to enforce least privilege and prevent data exfiltration.
Key takeaways
-
Model Agnosticism is Critical
5:01
Do not rely on a single LLM or harness, as the best model changes frequently. Utilizing open-weight models (like GLM 5.2) allows teams to stay in control of costs and maintain workflow continuity.
-
Agent Interfaces Must Be Universal
6:48
Agents should not be trapped on a single laptop or platform (e.g., Slack). The agent session must maintain context when moving between relevant interfaces like Slack, the desktop app, and GitHub.
-
External Signals Must Become Code
10:10
Treat all external signals—customer calls, meetings (e.g., a Google Meet bot), bug reports from Sentry, or emails—as inputs that can automatically trigger and prioritize work for the coding agent.
-
Work Must Be Visible Everywhere
9:09
To improve collaboration, agents should make their work visible across all platforms using standardized artifacts (screenshots or videos), eliminating context switching.
-
Use Isolated Cloud Environments
12:22
Running agents in a cloud sandbox is essential for security, enabling non-technical staff to trigger real work without having development environments on their local machines. This enforces the principle of least privilege.
