CLI reference

clawmetry status#

Local and cloud state. The command to run first when anything looks wrong.

clawmetry status

What it tells you#

• Whether the sync daemon is running, and for how long
• When it last ingested, and whether it is keeping up
• Store size and event count
• Which runtimes are detected
• Cloud sync state: connected or not, node id, endpoint, last push
• The resolved tier

Live mode#

clawmetry status --live

A single line that updates in place: sessions · tokens · cost · model · tokens per second. It is the thing to leave running in a spare pane while an agent works — you see spend accumulate in real time, which changes how people write prompts more than any report does.

--live and --json are mutually exclusive; --json wins and --live is ignored.

JSON#

clawmetry status --json | jq

The envelope covers daemon state, store state, runtime detection and cloud sync, so a wrapper can check health without screen-scraping.

# is the daemon alive?
clawmetry status --json | jq -e '.daemon.running' >/dev/null || echo "daemon down"

# how big is the store?
clawmetry status --json | jq '.store.bytes'

# which runtimes are actually producing data?
clawmetry status --json | jq '[.runtimes[] | select(.sessions > 0) | .id]'

The flag matches the sibling --json on tier, license, runtimes, features, channels, diagnose and verify-integrity, so a monitoring wrapper parses one style throughout.

Revealing the key#

clawmetry status --show-key

Prints the node's secret to the terminal. That means it lands in your shell history and any terminal-recording your setup does. Use it deliberately, and prefer reading it from the config file in scripts.

Common readings#