Clawdbot Logs

Analyze Clawdbot logs and diagnostics. Use when the user asks about bot performance, response times, errors, session stats, token usage, API costs, or wants to debug slow responses…

satriapamudji

@satriapamudji

What This Skill Does

Analyzes Clawdbot logs and diagnostics to inspect bot performance, response times, errors, session stats, token usage, and API costs. Provides shell commands and journalctl queries for debugging slow responses and configuration issues.

Replaces manually grepping through multiple log files and systemd journals by providing ready-made diagnostic scripts and targeted filtering patterns.

When to Use It

  • Check recent response times for the last 20 messages
  • Find errors or failures in the last hour of gateway logs
  • View current session token count and decide if a session compact is needed
  • Validate the Clawdbot configuration file for syntax errors
  • Parse session JSONL files to extract recent user messages
  • Monitor gateway service status and session state changes

Install

$ openclaw skills install @satriapamudji/clawdbot-logs

Clawdbot Logs & Diagnostics

Analyze Clawdbot performance, errors, and session data.

Quick Commands

Response Times (last N messages)

scripts/response-times.sh [count]

Recent Errors

journalctl --user -u clawdbot-gateway.service --no-pager --since "1 hour ago" | grep -iE "(error|fail|invalid)" | tail -20

Session Stats

scripts/session-stats.sh

Gateway Status

systemctl --user status clawdbot-gateway.service --no-pager

Config Validation

cat ~/.clawdbot/clawdbot.json | jq . > /dev/null && echo "Config valid" || echo "Config invalid"

Log Sources

SourceLocationContains
Journaljournalctl --user -u clawdbot-gateway.serviceSession state, errors, tool exec
Daily log/tmp/clawdbot/clawdbot-YYYY-MM-DD.logDetailed JSON logs
Session file~/.clawdbot/agents/main/sessions/*.jsonlFull conversation, token usage, costs
Sessions meta~/.clawdbot/agents/main/sessions/sessions.jsonCurrent session state, model info

Common Diagnostics

Slow Responses

  1. Check response times: scripts/response-times.sh 20
  2. Check token count in sessions.json: jq '.["agent:main:main"].totalTokens' ~/.clawdbot/agents/main/sessions/sessions.json
  3. If tokens > 30000, run /compact in Telegram or start new session

Config Errors

journalctl --user -u clawdbot-gateway.service --no-pager --since "10 minutes ago" | grep -i "invalid config"

API Costs (from session)

scripts/session-stats.sh

Useful Patterns

Filter journal by category

# Session state changes
journalctl --user -u clawdbot-gateway.service | grep "session state"

# Tool execution
journalctl --user -u clawdbot-gateway.service | grep "\[tools\]"

# Telegram activity
journalctl --user -u clawdbot-gateway.service | grep "\[telegram\]"

Parse session file for recent messages

tail -20 ~/.clawdbot/agents/main/sessions/*.jsonl | jq -r 'select(.message.role=="user") | .message.content[0].text' 2>/dev/null | tail -10

Top skills in this category