YC opens a control plane for agent fleets

Y Combinator open-sourced QM after running more than 50 internal agents. QM gives people and projects isolated workspaces with scoped memory, files, permissions, keychain views, scheduled jobs, web apps, and durable sandboxes. Why it matters: The hard problem is not spawning another agent. It is deciding which state persists, who can see credentials and files, which models are allowed, and where a sandbox stops. QM treats that operating layer as the product surface for a multi-agent company.

Try this: Open QM's deployment and security files. Make a one-page policy listing workspace, memory, file, credential, model, schedule, sandbox, and human-escalation boundaries; then verify each internal agent against that policy.