yc-software / qm

**A multiplayer agent harness for work. In Slack and on the web.** 
Run it in your own cloud, with your own models and keys.
Deploy · How it works · Security model · Customize · Contribute · Documentation
## Overview
Most agents are designed like personal assistants. You can make one work for a whole
company, but it quickly gets complex. QM is designed for startups. Employees each get
their own isolated workspace, and can also collaborate with the agent in channels, group messages, and projects.
Each person and each room has its own scoped memory, files, keychain view, permissions,
crons, web apps, and durable sandbox.
It's built with open source in mind. Pick your own harness and model and switch between
them. Pi and Claude Code both drive the same core, and Pi runs models from many
providers, so a deployment isn't tied to any single vendor.
## Setup
Tell your coding agent of choice `Let's deploy https://github.com/yc-software/qm`. From here, it should follow the deployment guide in this repo.
You can also try out a 3rd-party hosted version of QM here.
If you're an infra provider interested in offering a hosted version of QM, feel free to reach out.
## Features
- **Personal and shared scopes.** People customize the agent to be _theirs_, and still
 work with it collaboratively in Slack channels and projects.
- **Slack and web.** The same identity and configuration carries between Slack and the
 web app.
- **Admin control.** Set org-level configuration, security and sharing postures. Choose which
 harnesses and models are available.
- **Web apps.** Spin up custom internal apps and publish them to the right people.
- **Shared skills.** Skills are scope-owned and shareable by grant, with admin-gated
 promotion to the whole org and skill packs imported from git repositories.
- **Background work.** Crons, watches, and inbound webhooks work while you're away.
## What you can do with it
- Search internal notes, email, documents, databases, and the web together
- Build internal apps, publish them to the right people, and keep their data current
- Learn your writing voice from past sends, then triage your inbox on a schedule —
 labels and reply drafts included
- Work in an existing repository: run tests, open PRs, monitor CI, check system logs
- Track a project in a shared channel and post updates and follow-ups
## Architecture
 [code] 
For durability, set `DATABASE_URL` and `SESSION_STORE=postgres` — without it, sessions
live in process memory and vanish on restart. To exercise a branch against a real model and real Postgres, run
`npm run dev-instance:web` for web/admin or `npm run dev-instance:slack` for Slack.
Use `npm run dev-instance:both` when testing both surfaces together. Bare
`npm run dev-instance` defaults to web for new instances and preserves the surface
on reload. Switch an existing instance with an explicit surface command.
## How it works
Every turn runs through a central core, which can use a variety of models and harnesses
to generate th