QM

QM is a multi-agent chat workbench: you run skills, manage conversations, and coordinate agent runs from a first-party web UI. On Harnesser, QM ships in its production shape, with real sign-in and durable state, so it is ready for a team from day one.

What you get

Your QM harness comes with:

• The QM portal at https://<name>.harnesser.co, the single entry point for chat, admin, and sign-in
• QM’s own user management: sign-in by one-time email links, with roles and per-action authorization
• A durable database on your persistent disk for sessions, runs, and audit history
• Model access through the built-in gateway — or bring your own keys

First sign-in

QM signs users in with one-time links sent by email; there are no passwords.

1. Open https://<name>.harnesser.co and enter the email address you used for your Harnesser console account.
2. QM emails you a one-time sign-in link. Open it and you are in.

The console account that created the harness is seeded as the QM organization admin, and at first it is the only address allowed to sign in. Adding more sign-in addresses is not self-service yet; contact the operator to have teammate emails allowed on your instance.

Working in QM

Skills and configuration persist on your disk, so anything you set up survives restarts, and QM’s database keeps a durable record of sessions, runs, and audit history. Chat runs against the models behind the built-in gateway.

Two current limits:

• Chat history is held in memory in this version, so open conversations do not survive a restart. Skills, configuration, and the session, run, and audit records do.
• QM’s container-tool sandbox (turns that run inside Docker containers) is not available on Harnesser machines. Chat and QM’s in-core tools work normally.

Going public

A private QM harness is only reachable by you through the console session. Because QM brings its own sign-in, you can safely make it public and let your team reach the portal directly; QM’s login becomes the gate. See Public and private access.