How do I monitor qm agents?

Install ClawMetry (pip install clawmetry, or the one-liner installer at clawmetry.com/install.sh) and set CLAWMETRY_QM_DATABASE_URL to your qm Postgres URL. ClawMetry reads qm's sessions, session_entries, session_llm_requests, turn_metrics, and runs tables in read-only mode and renders sessions, tokens, cost, and the org-scope layer in one dashboard. No qm code change.

What does ClawMetry show for qm that Pi, OpenCode, Codex, and Claude Code do not?

The org-scope layer. qm delegates to Pi, OpenCode, Codex, and Claude Code as harnesses, and those child adapters can only see their own turn. ClawMetry's qm adapter surfaces scopeId, surface (slack, web, cli), threadRef, channelName, turn count, and last activity for every session, so you can see who in the org ran what, cron health across scopes, and scope-level token totals.

Does ClawMetry work with qm on Slack, on the web, or on the CLI?

All three. qm records the surface (slack, web, cli) on every session row; ClawMetry reads that column and lets you filter sessions and token cost by surface. The Slack path also carries the channel name so you can group qm activity by channel.

How much does ClawMetry cost for qm?

Free forever on your own machine (local dashboard at http://localhost:8900). ClawMetry Cloud starts at $9 per node per month (Starter) or $19 per node per month (Pro, which adds policy gates, evals, and per-run waste flags). The qm adapter itself is part of the Pro tier because qm delegates to Pi, OpenCode, Codex, and Claude Code, which are also Pro adapters.

Observability and governance for QM agents

Q: Is ClawMetry safe to point at production qm?

Yes. Every connection sets default_transaction_read_only=on before any SELECT, so a bug in ClawMetry cannot mutate qm's tables. All queries hit indexed paths (sessions_by_activity, session_entries_session_created), open a short-lived connection, run one SELECT, and close. You can also point CLAWMETRY_QM_DATABASE_URL at a read replica if your policy requires it.

See every qm turn, scope, and token as it happens. ClawMetry reads qm's Postgres tables in read-only mode and renders sessions, tokens, cost, and the org-scope layer in one dashboard. No qm code change.

17th supported runtime Reads Postgres tables directly Read-only, MVCC-safe Free trial

What ClawMetry sees on qm

qm (github.com/yc-software/qm, qm.ycombinator.com) is Y Combinator's open-source multiplayer agent harness: one Slack + web surface per org, per-scope sandboxes, and a central turn loop that delegates to Pi, OpenCode, Codex, and Claude Code. ClawMetry's qm adapter opens the same Postgres qm writes to and surfaces:

Sessions per scope, surface (slack, web, cli), thread reference, channel name, turn count, and last activity, from the sessions table.
Every entry: user messages, assistant turns, tool calls, tool results, and handoffs to child harnesses, from session_entries.
Token cost per session: normalised from session_llm_requests.usage_json (Anthropic and OpenAI shapes both handled), split into input, output, cache-read, and cache-write tokens.
Per-turn timing and rollups: TTFT, total ms, model calls, tool calls, from turn_metrics.
The org-scope layer: scopeId, surface, threadRef, channelName. That Pi, OpenCode, Codex, and Claude Code cannot see individually.

Source: the adapter is at clawmetry_pro/adapters/qm.py. Every SELECT it runs is in that file; the schema columns are captured verbatim from qm's own CREATE TABLE statements in src/sessions/postgres-session-store.ts and src/admin/postgres-metrics-sink.ts.

Enable it in about two minutes

1. Install ClawMetry

Pick the line that matches your OS. Windows users: paste the install.cmd line, not the shell one.

# macOS or Linux
curl -fsSL https://clawmetry.com/install.sh | bash

# Windows (cmd.exe or PowerShell)
curl -fsSL https://clawmetry.com/install.cmd -o install.cmd && install.cmd

2. Connect the daemon

clawmetry connect

3. Point at qm's database

ClawMetry reads CLAWMETRY_QM_DATABASE_URL first (so you can point at a read replica), then falls back to DATABASE_URL if unset.

export CLAWMETRY_QM_DATABASE_URL="$DATABASE_URL"

Open http://localhost:8900. Switch the runtime chip to QM. Every qm session, scope, and cost is there.

Start the free trial →

Safety: read-only by design

Every connection sets:

SET default_transaction_read_only = on;

before any SELECT. A bug in ClawMetry cannot mutate qm's tables. All queries hit indexed paths (sessions_by_activity, session_entries_session_created, turn_metrics_by_ts). Connections are opened per query and closed immediately, so a stalled query cannot pin a pool slot.

If your policy is stricter, point CLAWMETRY_QM_DATABASE_URL at a Postgres read replica. Nothing else in ClawMetry needs write access to qm's database.

What each tab shows for qm

Tab	What it shows	Scope
Sessions	Every qm session, sorted by last activity, with scope, surface, and token totals	All scopes, or filter by one
Brain	Live entries as they land: user messages, tool calls, handoffs to child harnesses	Whole node, or one session
Cost	Per-session, per-scope, per-hour token spend; cache-read vs uncached-input split	Runtime = qm, or all
Sub-agents	Which child harness (Pi, OpenCode, Codex, Claude Code) served each qm turn	Per session

How this compares to running qm alone

qm's own admin surface shows current runs and audit logs. What it does not show is real-time cost per hour across scopes, cache hit rate per session, or a kill-switch when a scope's turn is token-maxing. Those are the things a team running qm on a real budget needs on day one; they are what ClawMetry adds. See the cost-per-hour visibility page and the token-maxing page for how these work end to end.

All 19 runtimes ClawMetry observes

qm is one of 19. Free on every plan: OpenClaw, NVIDIA NemoClaw. Paid on Cloud Pro or Self-Hosted Pro: the rest.

OpenClaw NVIDIA NemoClaw NanoClaw PicoClaw Claude Code Codex Cursor Aider Goose opencode Qwen Code Hermes Pi Deep Agents n8n Antigravity GitHub Copilot Grok QM (this page)

Individual per-runtime pages are rolling out over the next few weeks. Ping vivek@clawmetry.com if there's one you want prioritised.