How do I monitor opencode sessions?

Install ClawMetry (pip install clawmetry). The daemon auto-detects opencode and renders every session, tool call, model, and token in one dashboard at http://localhost:8900.

Does ClawMetry catch opencode's parallel-provider double-charge?

Yes. When opencode fans a turn to Anthropic + OpenAI + local, each provider bills separately; ClawMetry shows the fan-out cost on the Cost tab, plus flags a session where the total provider bill is far larger than the returned tokens suggest.

Is ClawMetry safe against a running opencode?

Yes. ClawMetry only observes. It never writes to opencode, and it never blocks opencode while opencode is working.

Does ClawMetry work with opencode's TUI and CLI modes?

Yes. ClawMetry picks up both identically. Sessions are labelled with their surface (TUI or CLI).

How much does ClawMetry cost for opencode?

Free forever on your own machine. Cloud starts at $9/node/mo (Starter) or $19/node/mo (Pro).

OpenCode × ClawMetry

Observability and cost tracking for opencode

See every opencode session, tool call, and token as it happens. ClawMetry detects opencode automatically and renders sessions, tokens, cost, and per-provider routing in one dashboard. No SDK.

Supported runtime Zero config, auto-detected Read-only Free trial Official OpenCode site ↗

📦 631k+ installs 🌍 128+ countries ⭐ 392 on GitHub 🏆 #5 Product Hunt

What ClawMetry sees on opencode

Once ClawMetry is running, your opencode activity shows up as:

Sessions: started at, last activity, model, message count, per-session token totals.
Live activity: every tool call as it lands, with args and result. Turn-level tokens split.
Per-turn tokens: Per-turn tokens computed by opencode: input, output, cache-read, cache-write, reasoning.
Cost per session, per model, per hour: cache-aware where the model supports caching.
Multi-provider parallel routing (opencode fans a hard turn to multiple providers): the opencode-specific signal ClawMetry surfaces that generic dashboards do not.
Approval and kill switch: watch for token-maxing signals (message repeat, no-progress heuristic, cost-per-hour threshold), pause or kill before the next call.

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

Already have Python? pip works too; onboard is the interactive first-run wizard.

# Any OS with Python 3.9+
pip install clawmetry && clawmetry onboard

Or skip the terminal entirely and grab the desktop app: macOS (.dmg) · Windows (.exe) · Linux (.AppImage). It installs and updates ClawMetry for you.

2. Run the daemon

clawmetry

The daemon auto-detects opencode and starts reading immediately. No env var, no config, no runtime restart.

3. Open the dashboard

Open http://localhost:8900. Switch the runtime chip to opencode.

Start the free trial →

The one thing this catches that opencode alone does not

Left alone, opencode's failure mode is a fanned turn charged three times because every provider took the request. ClawMetry watches for it: cost per hour on the opencode runtime, message-repeat detection, and per-session token-growth curves. Set a threshold, and the approval queue pauses before the next call. Kill switch (Pro) stops it.