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.