注册并分享邀请链接,可获得视频播放与邀请奖励。

Sumanth (@Sumanth_077) “YC just open sourced their multi-agent harness! QM is the multiplayer agent harn” — TopicDigg

Sumanth 的个人资料封面
Sumanth 的头像
Sumanth
@Sumanth_077
加入 July 2021
0 正在关注    0 粉丝
YC just open sourced their multi-agent harness! QM is the multiplayer agent harness Y Combinator built and has been running internally across accounting, legal, events, and engineering. They used QM to build QM itself. The starting point was a fleet of 50+ Hermes agents - one personal assistant per employee. Managing that many separate agents became complex. QM came from asking a different question: instead of one agent per person, what if a company had one harness that worked for everyone? Most agents are designed like personal assistants. QM is designed for teams. Each employee gets their own isolated workspace with scoped memory, files, permissions, crons, and a durable sandbox. Those workspaces also connect in shared Slack channels and projects where people and the agent work together. The same identity and configuration carries between Slack and the web app. Admin controls which harnesses and models are available org-wide. Pi, OpenCode, Codex, and Claude Code all drive the same core, so a deployment isn't tied to any single vendor. Background work runs while nobody's watching. Crons and webhooks trigger tasks across the org. Skills are scope-owned and shareable by grant, with admin-gated promotion to the whole organization. YC is direct about where it stands: it's an experiment, it's early, and it has bugs. Key capabilities: • Multiplayer: personal workspaces + shared Slack channels and projects • Works natively in Slack and on the web • Vendor agnostic: Pi, OpenCode, Codex, Claude Code all supported • Per-scope memory, files, keychain, permissions, crons, and durable sandbox • Background crons and webhook triggers • Shareable skills with admin-gated org promotion • Three security postures: Strict, Auto, Dangerous 100% open source. The multiplayer harness problem is real and QM is a solid approach to it. The other harness problem most teams haven't named yet is context quality - what actually flows into the harness from your organization's systems determines everything that follows. Wrote a detailed breakdown on exactly that. I've also shared the link to QM in the replies!
显示更多