Local-first developer instrument

Your coding time, measured. Your AI, accounted for.

Local-first time tracking that finally separates your hours from your AI agents' — run time vs real work, all on your machine.

Detected AI tools
6
Daemon bind
127.0.0.1
Storage
SQLite
pulse://today
Animated pulse waveform resolving into a bar chart A heartbeat waveform traces local coding activity, ending as teal and coral bars for you and AI. YOU AI

AI writes more of your code every week. Do you actually know how much?

Three surfaces

One local signal, three ways to read it.

Code Pulse keeps the extension, desktop app, CLI, daemon, and MCP server aligned around the same local activity stream.

Editor surface

Automatic coding time with AI visibility in the same dashboard.

Heartbeat tracking, idle detection, per project/language/file breakdowns, charts, goals, streaks, focus sessions, CSV export, and an AI Tools panel for terminal and extension activity.

Show Dashboard Toggle Time Tracking Toggle Focus Session Show Goals
Code Pulse Dashboard
Dashboard 4h 12m tracked today
tracking on
Focus2h 48m
Streak11d
CSVready
AI Tools 6 scanners
Claude Code ran 3h 06m · worked 41m
OpenAI Codex ran 1h 18m · worked 22m
Cursor extension detected
Feature bento

Built for developers who want the accounting to be real.

Code Pulse records the local signals that matter without turning your workflow into another dashboard chore.

Run-vs-active time

Each AI tool gets uptime separated from real activity, so "ran 3h" can still mean "worked 37m".

6 AI tools detected

Terminal and extension scanners recognize the tools developers actually run.

Claude Code OpenAI Codex Cursor Cline Droid (Factory) Kilo

Goals & streaks

Daily and weekly goals keep your own coding rhythm visible.

Focus sessions

Start a focused window and keep the session separate from idle time.

Productivity scoring

Measure patterns without pretending raw hours are the whole story.

CSV export & heatmap

Take the raw local data with you, or inspect the week as a compact activity heatmap.

Privacy / local-first

Your data never leaves your machine.

Code Pulse has no cloud account, no telemetry pipeline, and no remote analytics service. Activity lands in a local SQLite database and stays there.

127.0.0.1:7842 Loopback-only daemon
0600 Auth token file mode
ed25519 Signed scanner registry
NO CLOUD No account or telemetry
How it works

Install once. Let the instrument run quietly.

  1. 1

    Install

    Add the Code Pulse VS Code extension and start the local platform when you want CLI, daemon, or MCP access.

  2. 2

    It tracks silently

    Editor heartbeats, terminals, and AI logs flow into the local daemon without sending data anywhere.

  3. 3

    See your pulse

    Read the signal in the extension dashboard, desktop app, CLI, or from an AI agent through MCP.

Download

Choose the surface you want to run first.

Start with the VS Code extension, add the desktop app when you want a dedicated command center, and use the CLI/daemon/MCP layer for local automation.

VS Code

Extension

Install the Marketplace extension for automatic coding-time tracking, goals, focus sessions, and the in-editor AI Tools panel.

Open Marketplace

Local VSIX: code-pulse-tracker-1.2.2.vsix

Desktop

Native app

Use the Tauri desktop dashboard for Timeline, Tokens, Recovery, AI Sources, and the You vs AI overview outside the editor.

GitHub Releases

Installers are produced by the desktop release workflow.

Local platform

CLI + daemon + MCP

Run the loopback daemon, query activity from the CLI, and expose local stats to MCP-capable AI agents without sending data to a cloud service.

Read setup docs

codepulse doctor verifies the local stack.

Start local

Start measuring your pulse.