24-hour timelines
See when you deep-worked — by project and by language. Heat intensity = focus density that hour.
Local-first coding analytics
Languages. Projects. Editors. AI lines vs human. Tokens. Cost. A living dashboard of your craft — stored on your machine, full history, forever free.
The product surface
Every panel is live data from your editor heartbeats — same screen you’ll open after install.
See when you deep-worked — by project and by language. Heat intensity = focus density that hour.
Coding · AI Coding · Docs · Tests — stacked daily so the shape of your week is obvious.
Agents · Editors · Languages · OS · Machines — donuts with exact time and share.
Each repo gets time, AI/human split, prompts, sessions, tokens, estimated spend by agent. Ranked. Color-coded.
Data density
If it happened in your editor, CodePulse can surface it — and keep it forever.
Built for agent-era work
Hours alone lie. CodePulse separates human edits from agent output, tracks prompts & sessions, and estimates spend — so you know which repos are tool-driven.
SQLite under ~/.codepulse. Heartbeats never required to leave localhost. You own the file.
Years of work stay queryable. Switch ranges: last week or all time. No artificial ceiling.
One install command. macOS login autostart. Dashboard at 127.0.0.1:3927. VS Code plugin in the box.
Get it running
macOS / Linux · installs release package, starts local server, opens the UI.
curl -fsSL https://codepulse.flowsrun.com/install.sh | bash
→ ~/.codepulse · dashboard http://127.0.0.1:3927 · optional VS Code vsix included
code --install-extension ~/.codepulse/apps/vscode/codepulse.vsix
# Cursor:
cursor --install-extension ~/.codepulse/apps/vscode/codepulse.vsix
Already tracking elsewhere? You can import historical heartbeats or point a compatible plugin at CodePulse — including tools that speak the common open heartbeat protocol (e.g. WakaTime plugins). Optional, not required.