Run a company-scoped multiplayer agent harness with QM
QM is an open-source agent harness for teams that want Slack, web, scoped memory, durable sandboxes, and model choice without tying the whole workflow to one vendor.
What you get from it
QM is worth a cautious look if your team wants agents to work across shared rooms, personal workspaces, Slack, and web surfaces without turning every employee's assistant into a separate unmanaged project.
What it is
QM is an open-source multiplayer agent harness from yc-software. Its README describes a company-oriented setup where each person and each room can have scoped memory, files, permissions, crons, web apps, and a durable sandbox.
Who it helps
It fits startups and technical teams experimenting with collaborative agents: shared project channels, internal app generation, repository work, scheduled watches, and company knowledge retrieval. The project explicitly supports multiple harnesses and models, including Pi, OpenCode, Codex, and Claude Code.
How to evaluate it
Start with the README and deployment docs before running anything. Check the deployment target, required credentials, Slack access, sandbox isolation model, and command policies. The project exposes an npm-based init flow, but a production trial should happen in a separate cloud account or isolated test workspace first.
Limits and risks
QM is infrastructure, not a small browser tool. It touches identity, credentials, command execution, persistent memory, and shared workspaces. Review SECURITY.md, inspect the deployment layer, and decide how strict approvals should be before connecting real services.
Access and pricing
The repository is public and lists an MIT license. Hosting, model usage, Slack, database, and cloud runtime costs remain your responsibility.
Sources
Discussion
Share practical experience, questions, or warnings with the community.
Sign in to join the discussion and vote on comments.
Sign in