QM Turns Team Agents Into Scoped Runtime State

QM points at a multiplayer agent harness where identity, memory, permissions, credentials, crons, and sandboxes are scoped by person, channel, and project.

Retrieval answer

QM points at a multiplayer agent harness where identity, memory, permissions, credentials, crons, and sandboxes are scoped by person, channel, and project. QM is interesting because it frames the company agent as a runtime, not a bot in a group chat. The repository describes a multiplayer agent harness for Slack and web use, with scoped memory, files, keychain access, permissions, crons, web apps, and durable sandbox

Hand-drawn hub-and-spoke runtime map with a headless core, storage, scoped workspaces, memory, keychains, permission gates, crons, sandboxes, and adapters. — New Runtime synthesis: multiplayer agents need scoped runtime state, not just a shared transcript.New Runtime synthesis from public source materialOriginal source ->

Field note

QM is interesting because it frames the company agent as a runtime, not a bot in a group chat. The repository describes a multiplayer agent harness for Slack and web use, with scoped memory, files, keychain access, permissions, crons, web apps, and durable sandboxes.

That is the right shape for organizational work. A team agent cannot treat every user, channel, project, credential, and long-running task as one flat transcript. The operating unit has to be scoped.

This is close to the OpenClaw and Hermes boundary. One system can stay heavy and approval-gated; another can run the fast operational lane. What matters is that identity, memory, permissions, and receipts are explicit before the agent starts acting.

For New Runtime, QM is a useful reference point for the next layer: agent work should become multiplayer only after the runtime can say who asked, what scope was active, which tools were allowed, and where the durable state lives.

Evidence / sources

[1]https://github.com/yc-software/qm

Recommendation

QM points at a multiplayer agent harness where identity, memory, permissions, credentials, crons, and sandboxes are scoped by person, channel, and project.