| name | clawprobe |
| description | Monitor OpenClaw agent health, token usage, API cost, context window, tool usage, todo progress, and sub-agents in real time. Use when you need to check your own status, inspect context utilization, estimate API costs, review tool usage patterns, check todo completion, or get optimization suggestions. Provides structured JSON output for programmatic self-monitoring. |
| metadata | {"openclaw":{"emoji":"🦀","homepage":"https://github.com/seekcontext/ClawProbe"}} |
clawprobe
Real-time observability for OpenClaw agents. Check health, token usage, API cost, context window, tool usage, todo progress, and optimization suggestions — all from the CLI.
Install
npm install -g clawprobe
clawprobe start
Core commands
| Command | What it does |
|---|
clawprobe status --json | Full health snapshot (session, model, context %, cost, alerts) |
clawprobe cost --week --json | API cost breakdown for the past week |
clawprobe session --json | Session breakdown: turns, tool usage, todos, sub-agents |
clawprobe context --json | Context window utilization and truncation warnings |
clawprobe suggest --json | Active optimization alerts with ruleId and action |
clawprobe compacts --json | List recent compaction events and lost content |
clawprobe top | Live auto-refreshing dashboard (human use) |
Recommended self-check workflow
Run at session start or before any expensive task:
STATUS=$(clawprobe status --json)
UTIL=$(echo $STATUS | node -e "process.stdin.resume();let d='';process.stdin.on('data',c=>d+=c);process.stdin.on('end',()=>console.log(JSON.parse(d).utilizationPct))")
echo "Context: $UTIL%"
Or in a single call:
clawprobe status --json
Key fields to act on:
utilizationPct ≥ 85 → compact soon or start a fresh session
suggestions[].ruleId === "tools-truncation" → TOOLS.md is being cut off
suggestions[].ruleId === "cost-spike" → today's spend is unusually high
daemonRunning: false → run clawprobe start to enable monitoring
Checking tool usage and todo progress
clawprobe session --json
Key fields in session JSON:
toolStats[].name / callCount / errorCount — which tools were called and any errors
todos[].content / status — todo list items (pending, in_progress, completed)
agents[].type / model / description — sub-agent invocations
Handling suggestions programmatically
clawprobe suggest --json
clawprobe suggest --dismiss memory-bloat --json
Schema introspection
When you need to know exact field names for any command:
clawprobe schema status
clawprobe schema cost
clawprobe schema
Error format
All errors under --json are structured — never colored text:
{ "ok": false, "error": "no_active_session", "message": "No active session found" }
Exit code is always 1 on error.
Cost note
Cost figures are estimates based on public model pricing. Verify exact amounts with your model provider's billing dashboard.