Skip to content

vivekchand/clawmetry

Folders and files

NameName
Last commit message
Last commit date

Latest commit

Β 

History

651 Commits
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 

Repository files navigation

🦞 ClawMetry

PyPI Downloads PyPI Downloads/week PyPI version GitHub stars License: MIT

ClawMetry - #5 Product of the Day on Product Hunt

See your agent think. Real-time observability for OpenClaw AI agents.

One command. Zero config. Auto-detects everything.

pip install clawmetry && clawmetry

Opens at http://localhost:8900 and you're done.

Flow Visualization

What You Get

  • Flow β€” Live animated diagram showing messages flowing through channels, brain, tools, and back
  • Overview β€” Health checks, activity heatmap, session counts, model info
  • Usage β€” Token and cost tracking with daily/weekly/monthly breakdowns
  • Sessions β€” Active agent sessions with model, tokens, last activity
  • Crons β€” Scheduled jobs with status, next run, duration
  • Logs β€” Color-coded real-time log streaming
  • Memory β€” Browse SOUL.md, MEMORY.md, AGENTS.md, daily notes
  • Transcripts β€” Chat-bubble UI for reading session histories

Screenshots

🧠 Brain β€” Live agent event stream

Brain tab

πŸ“Š Overview β€” Token usage & session summary

Overview tab

⚑ Flow β€” Real-time tool call feed

Flow tab

πŸ’° Tokens β€” Cost breakdown by model & session

Tokens tab

🧬 Memory β€” Workspace file browser

Memory tab

πŸ” Security β€” Posture & audit log

Security tab

Install

One-liner (recommended):

curl -sSL https://raw.githubusercontent.com/vivekchand/clawmetry/main/install.sh | bash

pip:

pip install clawmetry
clawmetry

From source:

git clone https://github.com/vivekchand/clawmetry.git
cd clawmetry && pip install flask && python3 dashboard.py

Configuration

Most people don't need any config. ClawMetry auto-detects your workspace, logs, sessions, and crons.

If you do need to customize:

clawmetry --port 9000              # Custom port (default: 8900)
clawmetry --host 127.0.0.1         # Bind to localhost only
clawmetry --workspace ~/mybot      # Custom workspace path
clawmetry --name "Alice"           # Your name in Flow visualization

All options: clawmetry --help

Supported Channels

ClawMetry shows live activity for every OpenClaw channel you have configured. Only channels that are actually set up in your openclaw.json appear in the Flow diagram β€” unconfigured ones are automatically hidden.

Click any channel node in the Flow to see a live chat bubble view with incoming/outgoing message counts.

Channel Status Live Popup Notes
πŸ“± Telegram βœ… Full βœ… Messages, stats, 10s refresh
πŸ’¬ iMessage βœ… Full βœ… Reads ~/Library/Messages/chat.db directly
πŸ’š WhatsApp βœ… Full βœ… Via WhatsApp Web (Baileys)
πŸ”΅ Signal βœ… Full βœ… Via signal-cli
🟣 Discord βœ… Full βœ… Guild + channel detection
πŸŸͺ Slack βœ… Full βœ… Workspace + channel detection
🌐 Webchat βœ… Full βœ… Built-in web UI sessions
πŸ“‘ IRC βœ… Full βœ… Terminal-style bubble UI
🍏 BlueBubbles βœ… Full βœ… iMessage via BlueBubbles REST API
πŸ”΅ Google Chat βœ… Full βœ… Via Chat API webhooks
🟣 MS Teams βœ… Full βœ… Via Teams bot plugin
πŸ”· Mattermost βœ… Full βœ… Self-hosted team chat
🟩 Matrix βœ… Full βœ… Decentralized, E2EE support
🟒 LINE βœ… Full βœ… LINE Messaging API
⚑ Nostr βœ… Full βœ… Decentralized NIP-04 DMs
🟣 Twitch βœ… Full βœ… Chat via IRC connection
πŸ”· Feishu/Lark βœ… Full βœ… WebSocket event subscription
πŸ”΅ Zalo βœ… Full βœ… Zalo Bot API

Auto-detection: ClawMetry reads your ~/.openclaw/openclaw.json and only renders the channels you've actually configured. No manual setup required.

Docker Deployment

Want to run ClawMetry in a container? No problem! 🐳

Quick start with Docker:

# Build the image
docker build -t clawmetry .

# Run with default settings
docker run -p 8900:8900 clawmetry

# Or with your OpenClaw workspace mounted
docker run -p 8900:8900 \
  -v ~/.openclaw:/root/.openclaw \
  -v /tmp/moltbot:/tmp/moltbot \
  clawmetry

Docker Compose example:

version: '3.8'
services:
  clawmetry:
    build: .
    ports:
      - "8900:8900"
    volumes:
      - ~/.openclaw:/root/.openclaw:ro
      - /tmp/moltbot:/tmp/moltbot:ro
    restart: unless-stopped

Note: When running in Docker, make sure to mount your OpenClaw workspace and log directories so ClawMetry can auto-detect your setup.

Requirements

  • Python 3.8+
  • Flask (installed automatically via pip)
  • OpenClaw running on the same machine (or mounted volumes for Docker)
  • Linux or macOS

NemoClaw / OpenShell Support

ClawMetry automatically detects NemoClaw β€” NVIDIA's enterprise security wrapper for OpenClaw that runs agents inside sandboxed OpenShell containers.

No extra configuration is needed in most cases. The sync daemon auto-discovers session files whether they live in ~/.openclaw/ on the host or inside an OpenShell container.

How it works

ClawMetry detects NemoClaw in two ways:

  1. Binary detection β€” checks for the nemoclaw CLI and runs nemoclaw status to get sandbox info
  2. Container detection β€” scans running Docker containers for openshell, nemoclaw, or ghcr.io/nvidia/ images, then reads sessions via volume mounts or docker cp

Session files synced from NemoClaw containers are tagged with runtime=nemoclaw and container_id metadata in the cloud dashboard, so you can tell them apart from standard OpenClaw sessions at a glance.

Recommended setup: sync daemon on the HOST

For the best experience, run ClawMetry's sync daemon on the host machine (not inside the sandbox). This avoids NemoClaw network policy restrictions.

# On the host (outside the sandbox)
pip install clawmetry
clawmetry connect
clawmetry sync

The sync daemon will automatically find sessions inside any running OpenShell containers.

Optional: explicit sandbox name

If auto-detection doesn't work, point ClawMetry at the right sandbox:

export NEMOCLAW_SANDBOX=my-sandbox-name
clawmetry sync

Running inside the sandbox (advanced)

If you must run the sync daemon inside the OpenShell sandbox, add this egress rule to your NemoClaw network policy so it can reach the ClawMetry ingest API:

# nemoclaw-policy.yaml
network:
  egress:
    - host: ingest.clawmetry.com
      port: 443
      protocol: https

Apply with:

nemoclaw policy apply --file nemoclaw-policy.yaml

Ports and endpoints

Endpoint Port Protocol Required
ingest.clawmetry.com 443 HTTPS Yes (sync daemon β†’ cloud)
localhost:8900 8900 HTTP Yes (local dashboard UI)
Docker socket (/var/run/docker.sock) β€” Unix socket For container session discovery

The sync daemon only makes outbound HTTPS calls to ingest.clawmetry.com. No inbound ports are required.


Cloud Deployment

See the Cloud Testing Guide for SSH tunnels, reverse proxy, and Docker.

Testing

This project is tested with BrowserStack.

BrowserStack

Star History

Star History Chart

License

MIT


🦞 See your agent think
Built by @vivekchand Β· clawmetry.com Β· Part of the OpenClaw ecosystem

About

See your agent think. Real-time observability dashboard for OpenClaw AI agents.

Topics

Resources

License

Contributing

Security policy

Stars

Watchers

Forks

Packages

 
 
 

Languages