Claw Monitor

Use the clawmonitor CLI/TUI to inspect OpenClaw sessions, model health, token usage, and gateway service health.

ClawMonitor (OpenClaw monitoring)

Use this skill when the user asks questions like:

• “Did my agent finish? Why no feedback?”
• “Which session/thread received the last message, and when?”
• “Is the agent working, interrupted, or stuck? Any delivery failures?”
• “Which model is failing, and is the problem the provider or OpenClaw itself?”
• “Which session burned the most tokens recently?”
• “Do we have zombie/helper processes or a dirty gateway cgroup?”

Preconditions

• This skill runs on a machine that has OpenClaw state at ~/.openclaw/.
• clawmonitor is installed on that same machine.

Preflight (recommended)

Before using the commands below, verify the binary exists and can read local OpenClaw state:

bash

clawmonitor --version
clawmonitor init --non-interactive || true
clawmonitor status --format md

If clawmonitor is missing, or status fails, install it first.

Install:

bash

pip install -U clawmonitor

Alternative installs:

• pipx:

  bash

  pipx install clawmonitor
  

• Virtualenv:

  bash

  python3 -m venv .venv
  . .venv/bin/activate
  pip install -U pip
  pip install clawmonitor
  

Notes:

• Some OpenClaw environments intentionally disallow installing packages at runtime. If installs are blocked, ask the user to install clawmonitor on the host first.
• clawmonitor init writes config under ~/.config/clawmonitor/config.toml and is safe to re-run.

Core commands

0) Tree view (who owns which sessions)

If you suspect ACP/subagent routing issues (for example Telegram thread bindings), start with:

bash

clawmonitor tree

1) Status (Markdown)

Show the core status table:

bash

clawmonitor status --format md

For a more verbose table including task/message previews:

bash

clawmonitor status --format md --detail

2) Model health

Probe configured models directly and/or through OpenClaw:

bash

clawmonitor models --format md

Useful variants:

bash

clawmonitor models --mode direct --format json
clawmonitor models --mode openclaw --timeout 20

3) Drill down on one session

Export a redacted report for a single session key:

bash

clawmonitor report --session-key 'agent:main:main' --format md

4) Nudge (ask the session to report progress)

Send a progress request into the session:

bash

clawmonitor nudge --session-key 'agent:main:main' --template progress

5) Full TUI for interactive inspection

Run the TUI when you need interactive triage:

bash

clawmonitor tui

Important TUI keys:

• v: cycle Sessions / Models / System
• s: jump directly to System
• h: toggle right-side Status / History
• u: cycle token windows (now / 1d / 7d / 30d)
• r: refresh current active surface
• z: cycle pane widths
• Z: fullscreen detail
• o: open the English operator note in System view

Troubleshooting quick wins

• If clawmonitor status shows DELIVERY_FAILED or NO_FEEDBACK, export a report next:

  bash

  clawmonitor report --session-key 'agent:main:main' --format md
  

• If model checks disagree, separate direct provider path from OpenClaw path.

• If Telegram looks bound to the wrong session key, run clawmonitor tree and follow the bound session instead of assuming agent:main:... is the active path.

• If the problem is service-level, use the TUI System view and summarize risk, reclaimable memory estimate, and whether zombies/orphans were detected.

• If the TUI is unavailable, fall back to clawmonitor status --format md --detail plus clawmonitor models --format md.

Reply guidelines

• Prefer --format md outputs for IM replies.
• If status shows DELIVERY_FAILED or NO_FEEDBACK, include the relevant sessionKey and recommend a report export next.
• If token questions are time-windowed, mention whether the number is a current session snapshot or a 1d / 7d / 30d Gateway usage range.
• Avoid pasting raw gateway logs unless the user asks; use clawmonitor report which redacts common secrets.