We Built a Scalable Agent Sandbox

2026-08-25 · source · source ↗ · raw capture · wiki page

A CloudSquid newsletter post describing how the team scaled agent-driven workflows across enterprise data — PDFs, CSVs, Excel, and SFTP exports from legacy systems with no APIs — without giving up governance and access controls.

The Problem

A single agent works fine in a single workflow. At 100 agents running in parallel against the same enterprise data, structural limits appear: agents overwrite each other's work, produce conflicting results, and — in a recent Anthropic multi-agent study the author cites — even start "turf wars."

Three approaches, then a virtual file system

The final design: one isolated file store (Google Cloud), and for every agent task an isolated, permissioned copy of only the files that task may touch. Each agent reads what it's permitted to read, writes what it's permitted to write, and can't see what's hidden. On completion, changes sync back to the true source in a controlled, ordered way — no race conditions, no silent overwrites, fully auditable. Agent count is decoupled from collision risk, because collision was never possible.

The counter-intuitive payoff

Sequential hand-offs — "Agent A must finish before Agent B starts" — turn out to be almost never necessary. With the workspace configured correctly upfront (Standard Operating Procedures), a hundred agents complete a reconciliation task in a single pass with no coordination overhead.