PicoClaw dashboard: observability and cost tracking

See every PicoClaw session, tool call, and per-provider token cost as it happens. ClawMetry detects PicoClaw automatically and prices every call, so sessions on providers PicoClaw itself does not report tokens for still get cost attribution.

See ClawMetry with PicoClaw

What ClawMetry sees on PicoClaw

Once ClawMetry is running, your PicoClaw 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-provider usage extracted from PicoClaw's provider messages plus a loopback LLM shim log for hosted VMs, so managed-VM sessions with no self-reported tokens still get cost attribution.
• Cost per session, per model, per hour: cache-aware where the model supports caching.
• Per-provider cost attribution (PicoClaw itself is token-blind on many providers): the PicoClaw-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 PicoClaw 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 PicoClaw.

The one thing this catches that PicoClaw alone does not

Left alone, PicoClaw's failure mode is a session that reads $0 on the Cost tab because the underlying provider does not report tokens. ClawMetry watches for it: cost per hour on the PicoClaw 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.

Starred by the people building AI

Engineers and founders from OpenAI, Google, PostHog and more have starred ClawMetry on GitHub. One of them helped build it.

Peter SteinbergerOpenAI

Creator of OpenClaw and founder of PSPDFKit, now at OpenAI.

Matt Van HornJune · Weber

Co-founder of June, the smart oven acquired by Weber. ClawMetry contributor.

Alex KrentselGoogle

Systems research engineer at Google and PhD student at UC Berkeley.

Manoel Aranda NetoPostHog

Software engineer at PostHog, previously mobile SDKs at Sentry.

Kody KendallLlamaPress AI

Co-founder of LlamaPress AI, an open-source AI web-app builder.

All 31 runtimes ClawMetry observes

PicoClaw is one of them; the other 30 are listed below. Free on every plan: OpenClaw, NVIDIA NemoClaw, Goose. Paid on Cloud Pro or Self-Hosted Pro: the rest.

Every runtime on one page, with what each one can and cannot show →