What data does ClawPulse collect?

Only aggregate numbers per day (token counts, model/tool usage, costs, message counts, session counts). No message content, file paths, tool arguments, or personal data is collected.

How do I authenticate?

Choose interactive device flow via clawpulse setup or supply an existing GitHub token in ~/.clawpulse/config.json; credentials are not stored in plain text beyond the config file.

Can I disable auto-push?

Yes. Auto-push is implemented via cron jobs and is optional; you can run clawpulse push manually whenever you want.

ClawPulse

Use Caution

@pierreeurope

npx machina-cli add skill @pierreeurope/clawpulse --openclaw

Files (1)

SKILL.md

2.9 KB

ClawPulse - Community Analytics for OpenClaw

Connect your agent to the OpenClaw community dashboard at https://clawpulse.vercel.app

Setup (Agent does this automatically)

Step 1: Install CLI

npm install -g openclaw-pulse

Step 2: Authenticate

The agent needs a GitHub token to push stats. Two options:

Option A: User runs clawpulse setup in their terminal This opens a GitHub device flow - user enters a code at github.com/login/device.

Option B: Agent uses existing GitHub token If the user has gh CLI authenticated, extract the token:

TOKEN=$(gh auth token)
mkdir -p ~/.clawpulse
echo "{\"apiUrl\":\"https://clawpulse.vercel.app\",\"githubToken\":\"$TOKEN\"}" > ~/.clawpulse/config.json

Step 3: Push stats

clawpulse push

This collects session stats from ~/.openclaw/agents/main/sessions/*.jsonl and pushes aggregate numbers to the ClawPulse API. No message content is ever collected.

Step 4: Set up auto-push via OpenClaw cron

Create TWO cron jobs for auto-push at midnight and noon:

{
  "name": "ClawPulse Push (midnight)",
  "schedule": { "kind": "cron", "expr": "0 0 * * *" },
  "payload": { "kind": "agentTurn", "message": "Run: clawpulse push --silent" },
  "sessionTarget": "isolated",
  "delivery": { "mode": "none" }
}

{
  "name": "ClawPulse Push (noon)",
  "schedule": { "kind": "cron", "expr": "0 12 * * *" },
  "payload": { "kind": "agentTurn", "message": "Run: clawpulse push --silent" },
  "sessionTarget": "isolated",
  "delivery": { "mode": "none" }
}

What Gets Collected (Privacy)

Only aggregate numbers per day:

Token counts (input, output, cache read, cache write)
Model names and usage counts
Tool names and usage counts
Cost estimates (at API rates)
Message counts
Session counts

Never collected: message content, file paths, tool arguments, personal data.

Commands

Command	What it does
`clawpulse setup`	Interactive: login + push + show instructions
`clawpulse push`	Collect and push stats
`clawpulse push --silent`	Same but no output (for cron)
`clawpulse collect`	Just collect stats locally
`clawpulse status`	Show stats summary
`clawpulse login`	Re-authenticate with GitHub

Dashboard

Personal: https://clawpulse.vercel.app/dashboard (after login)
Community: https://clawpulse.vercel.app
Leaderboard: https://clawpulse.vercel.app/community

Source

npm: https://www.npmjs.com/package/openclaw-pulse
GitHub: https://github.com/pierreeurope/clawpulse

Source

git clone https://clawhub.ai/pierreeurope/clawpulseView on GitHub

Overview

ClawPulse is a community analytics dashboard for OpenClaw. It automatically collects aggregate token stats (no message content) from your OpenClaw sessions and pushes them to clawpulse.vercel.app. Use the dashboard to compare with the community and track the pulse of OpenClaw.

How This Skill Works

The agent installs the openclaw-pulse CLI, authenticates with a GitHub token or via device flow, and runs clawpulse push to send aggregated metrics. It reads session data from ~/.openclaw/agents/main/sessions/*.jsonl and pushes totals to the ClawPulse API, never including message content. You can also set up two cron jobs to auto-push at midnight and noon.

When to Use It

When you want visibility into aggregate token stats without exposing message content
When you need a centralized dashboard to compare your activity with the community
When you want automated daily and noon updates to ClawPulse via cron
When you want to monitor model/tool usage and related costs at a glance
When you want a privacy-preserving view of OpenClaw activity trends

Quick Start

Step 1: npm install -g openclaw-pulse
Step 2: Run clawpulse setup and authenticate (device flow) or configure ~/.clawpulse/config.json with a GitHub token
Step 3: Run clawpulse push to send aggregate stats; optionally add two cron jobs for midnight and noon auto-push

Best Practices

Securely store your GitHub token and prefer device-flow setup for initial authentication
Use clawpulse push --silent for cron-based auto-push to reduce output noise
Verify the data shown in ClawPulse dashboards aligns with local session files
Regularly review privacy settings: only aggregate numbers are sent
Test setup with clawpulse collect before enabling automatic pushes

Example Use Cases

A developer team monitors daily token counts and model usage to benchmark OpenClaw adoption
An individual compares personal OpenClaw activity against the community leaderboard on ClawPulse
An ops engineer enables two cron jobs to keep ClawPulse up-to-date at midnight and noon
A user authenticates with GitHub token and pushes initial stats to establish a baseline
A product manager tracks cost estimates and usage trends across agents via the dashboard

Frequently Asked Questions

Add this skill to your agents