@ctatedev: from one agent to a graph of agents that message each other

Vercel's Chris Tate described how his setup grew from local agents to cloud agents, then cloud agents with sub-agents, and now a graph: each agent has its own sandbox, credentials stay outside the sandboxes, agents message each other, changes to GitHub need approval and sessions survive disconnects. He uses Vercel's own tools for this because he works there, so read it as a practitioner's design rather than a neutral review.

Why it mattersThe safety rules are the takeaway for anyone running agents: keep passwords and keys out of the agent's reach, give each agent its own space, and require approval for anything that changes live systems.

How we knowCompany figures are labelled as their own claims; anything we couldn't verify is labelled as a report or a claim.