DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to deploy a shared agent for your team in Slack and web with QM

Stand up a QM instance in your own cloud that teammates reach through Slack and the web app.

Credentials. Initialization asks for connector credentials and Slack access, so keep all secrets out of the repository and in your deployment's secret handling.

Who it is forA startup operator or engineer who wants one agent the whole team can use, and is comfortable running a deployment in their own cloud account.

The problemMost agents are built for one person. Teams need an agent with separate private workspaces per person and shared rooms, without handing company data to a third-party service.

The outcomeA deployed QM instance with web sign-in, optional Slack access, durable Postgres-backed sessions, and a verified live deployment.

What you need first

  • Your own cloud account for the deployment, as the README says each deployment runs in the operator's own cloud
  • Your own model keys and provider choice, since the README says deployments use your own models and keys
  • Node.js and npm to run the qm CLI and npm install (inferred from the npm commands in the README)
  • A Postgres database for durable sessions, set through DATABASE_URL
  • Optional: a Slack workspace where you can grant access, if you want Slack rather than web only

Steps

  1. Create an empty organization-owned deployment repository, following the README's advice to make it a deployment repository that depends on @yc-software/qm.
  2. Run npm exec --yes --package=@yc-software/qm@latest -- qm init . --org <org> --target <target>. The README leaves the --org and --target values blank, so fill in your organization name and deployment target. (inferred, check the README)
  3. Run npm install.
  4. Follow the deployment skill that initialization creates to set up infrastructure, web sign-in, connector credentials, and optional Slack access.
  5. Set DATABASE_URL and SESSION_STORE=postgres so sessions survive restarts, then complete the live verification step.

Prompt for your agent

Using the repository yc-software/qm, deploy a QM instance for <organization name> into <cloud account or target> by following its deployment guide. Report the web app address and the result of the live verification step. Verify that you can sign in to the web app before reporting the deployment as complete.

Caveat. The README does not say how long deployment takes or which cloud providers are supported beyond the linked guides, so check docs/getting-started.md and deployment.md before you start.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page