claude-pulse

Claude Pulse

One command. Global memory for Claude Code.

npx claude-pulse init

Claude Pulse captures every session, every decision, and every line of code across all your projects — automatically, locally, and queryable anytime. It gives Claude Code a persistent memory and gives you a dashboard to see your work.

No cloud. No accounts. No data leaves your machine.

What it does

Feature	How it works
Session tracking	Every start, stop, and tool call recorded automatically
Code metrics	Lines added/removed per file, per session, per day
Brain layer	Structured progress, decisions, and blockers captured at session end
Smart gating	Only asks for summaries on meaningful sessions — trivial ones auto-close
Cross-project context	Claude knows what you did in other projects when you start a session
Knowledge capture	Store patterns, fixes, and context mid-session with /pulse-remember
Audit trail	User identity, diff capture, and exportable records for compliance
Dashboard	Visual overview at localhost:3141 — activity, brain, projects, timeline

How to set it up

What you need

1. Claude Code (install guide)
2. Node.js 18+ (nodejs.org)
3. jq and sqlite3

# macOS
brew install jq sqlite3

# Ubuntu/Debian
sudo apt install jq sqlite3

Install

git clone https://github.com/Clemens865/Claude-Pulse.git
cd Claude-Pulse
npm install
npx claude-pulse init

That's it. Claude Pulse is now active for all projects. Use Claude Code normally — everything is captured in the background.

View your dashboard

npx claude-pulse start

Open http://localhost:3141.

The Dashboard

Overview

Key numbers at a glance: total sessions, net lines written, hours spent, active projects, streaks. Daily activity for the last 14 days. Top tools, skills, and frameworks.

Brain

A searchable timeline of your reasoning — not just your code. Structured entries for progress, decisions, blockers, patterns, and fixes. Filterable by type and project. This is the log of your thinking across sessions.

Projects

All projects ranked by activity. Click any project for session history, most-edited files, daily breakdowns.

Timeline

90-day GitHub-style heatmap. Darker squares = more active days.

Session Detail

Full event-by-event replay of any session. Every edit shows an expandable diff view. User identity (who@hostname) displayed when available.

Settings

Database info, record counts, and an export section with project/date filtering. Download your data as JSON or CSV anytime.

Commands

Terminal

Command	What it does
npx claude-pulse init	Set up hooks and database (safe to re-run)
npx claude-pulse start	Open the dashboard
npx claude-pulse status	Quick terminal summary
npx claude-pulse doctor	Health check — verify everything works
npx claude-pulse export	Export data as JSON, CSV, or NDJSON
npx claude-pulse verify	Audit integrity check
npx claude-pulse uninstall	Remove hooks (data preserved)

Export supports filtering:

claude-pulse export --format json --start 2026-03-01 --end 2026-03-31
claude-pulse export --format csv --table insights

Slash commands (inside Claude Code)

These work globally — any project, any directory:

Command	What it does
/pulse-projects	List all tracked projects with stats
/pulse-projects my-app	Details and insights for a specific project
/pulse-latest	Last 3 days of work across all projects
/pulse-latest 7	Last 7 days
/pulse-insights	Overview of all insights
/pulse-insights type:decision	All decisions you've made
/pulse-insights type:blocked	All current blockers
/pulse-insights auth	Search insights by keyword

Remembering things

Some knowledge emerges mid-session. /pulse-remember captures it:

/pulse-remember fix: sqlite3 needs absolute paths on macOS
/pulse-remember pattern: all API routes use getDb() singleton
/pulse-remember context: deploy freeze next week for mobile release

Claude distills your input into a concise summary and stores both layers:

• Content — Claude's clean one-liner (shown in dashboard)
• Reasoning — your original words (preserved for context)

These show up as "Knowledge" at your next session start — before yesterday's progress, because accumulated knowledge is more valuable.

Audit trail

Claude Pulse captures a complete activity trail suitable for AI code audits: