---
title: status
description: clawmetry status — the daemon, store and cloud state at a glance, the live one-line status bar, and the JSON envelope for scripting.
keywords: clawmetry status, agent daemon status, clawmetry live status bar
eyebrow: CLI reference
---

# `clawmetry status`

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

```bash
clawmetry status
```

| Flag | Effect |
|---|---|
| `--json` | Emit the status snapshot as JSON instead of the human table |
| `--live` | A live one-line status bar. Ctrl-C to exit. |
| `--show-key` | Reveal the secret key |

## 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

```bash
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

```bash
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.

```bash
# 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

```bash
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

| Status says | Do this |
|---|---|
| Daemon not running | `clawmetry sync` |
| Daemon running, last ingest hours ago | `DEBUG=1 clawmetry sync --foreground` and read the output |
| Runtimes detected, zero sessions | The runtime has not written anything, or a session limit is in play |
| Cloud connected, last push old | Check network, then `clawmetry diagnose` |
| Store growing fast | [Retention](/docs/data/retention/) |