Y Combinator Open-Sourced QM: A Multiplayer Agent Harness for Slack and the Web
YC open-sourced QM, their internal multiplayer agent harness. Our take at Automate Digital: the harness is the product, and most teams are still polishing demos.
Y Combinator open-sourced QM (Quartermaster), the multi-agent harness it uses across accounting, legal, events, and engineering. MIT license. Early. Buggy. Explicitly experimental.
Our reaction at Automate Digital was not "another framework." It was relief. Finally, a serious org is publishing the boring production layer that actually determines whether agents survive contact with real departments.
What QM is
QM is a multiplayer agent harness for Slack and the web. People and rooms get isolated memory, file storage, permissions, scheduled tasks, and sandboxes where tools persist. Pi, OpenCode, Codex, and Claude Code can drive the same core. TypeScript/Node/Fastify, Slack via Bolt, optional Vite + Lit UI.
Notice what YC did not open-source: a new model. They open-sourced tenancy, persistence, surface flexibility, and vendor independence. That tells you where the scarce competence sits.
Security as a first-class feature
Three org security postures gate tool calls. Destructive commands denied by default. Human-approval hooks can pause sensitive actions. This matches how we ship client systems: autonomy with brakes, not autonomy as branding.
If your "agent platform" cannot answer who can delete what in which room, you do not have a platform. You have a demo with Slack credentials.
Our take: stop worshipping the model loop
Most agent frameworks obsess over the model loop. QM obsesses over multi-tenancy, memory, permissions, and harness-agnostic drivers. YC runs it across accounting, legal, events, and engineering, including using QM to build QM.
That is the same bias we bring to agency automation. A CRM agent that drafts outreach is easy to prototype. A CRM agent that respects client boundaries, keeps room-scoped memory, schedules follow-ups, and survives staff turnover is the product. Harness work is where hours and risk actually get managed.
What we will steal (openly)
- Harness-agnostic agent drivers so model swaps do not rewrite business logic
- Room/person isolation as the default mental model for agency multi-client work
- Human approval as a first-class hook, not a bolted-on afterthought
We may not adopt QM wholesale. We will absolutely borrow its priorities. Open source at this layer raises the floor for everyone building production agents, including us.
Bottom line
YC did not gift the industry a smarter chatbot. They published organisational infrastructure for AI labour. At Automate Digital, that is the conversation we want the market to have: less model theatre, more harness engineering.
Sources: MarkTechPost.