Free & Open Source · AGPL-3.0

The missing analytics layer
for Claude Code

See exactly what Claude is doing — token usage, estimated costs, sessions, and insights across all your projects, right inside VS Code.

Token usage comes from Claude's local session logs. Costs are estimated from detected model pricing and may differ from Anthropic billing.

Claude Code Dashboard — overview of token usage, estimated costs, and session analytics

Everything you need to understand your Claude usage

Built for Claude Code power users who want full visibility into how they work with AI, with local token tracking and clearly labeled estimated cost.

📊

Real-Time Usage

Watch token counts tick up as Claude works. Live session detection via process monitoring — no more stale numbers.

💰

Cost Tracking

Per-session and per-project estimated cost using local token usage, detected model families, and a bundled pricing table. Set monthly budgets with 80% / 100% alerts.

🧠

Session Intelligence

See the first prompt of every session as a preview. Extended thinking sessions flagged with ⚡. Cache hit rates surfaced.

🤖

Subagent Visibility

When Claude spawns subagents via the Task tool, their token costs roll up to the parent session so nothing is hidden.

📁

File Explorer

Browse every file Claude touched in a project. See which files get the most attention across sessions.

🔒

Fully Local

Reads only from ~/.claude/ on your machine. Zero network requests. Zero telemetry. Your data never leaves your computer.

Every view you need

From a high-level command center to project-level drill-downs, the dashboard is built to help you understand how Claude actually works across your day.

Dashboard Overview
Command Center

Dashboard Overview

A single place for usage, estimated cost, and session visibility across your Claude projects.

Charts & Trends
Charts & Trends
Track token usage and activity patterns without leaving your editor.
Insights & Heatmaps
Insights & Heatmaps
See prompt mix, tool usage, efficiency metrics, and hot spots at a glance.
Project Drill-Down

Go from trends to the actual work

Sessions, commands, files, tools, and project instructions all stay visible in one place, so you can move from “what happened?” to “where did it happen?” quickly.

6 detailed project views
Session History
Session History
Review prompts, timing, token counts, and subagent activity per session.
Weekly Breakdown
Weekly Breakdown
Understand weekly throughput, estimated spend, and day-by-day usage patterns.
CLAUDE.md Context
CLAUDE.md Context
Surface project instructions and Claude-specific context alongside usage data.
Slash Commands
Slash Commands
Inspect command usage and keep reusable workflows easy to reference.
Tool Usage
Tool Usage
Break down which tools Claude uses most and where the work is happening.
File Explorer
File Explorer
See which files Claude touched most and navigate project activity faster.
Installation

Zero setup. Just install and go.

Claude Code Dashboard reads the session files Claude already writes to ~/.claude/projects/. No API key. No config. No account.

Displayed cost is estimated locally from session token usage, model detection, and a bundled pricing table. It is useful for visibility, but not invoice-grade billing.

1
Install the extension
Search for "Claude Code Dashboard" in the VS Code Extensions panel.
2
Open the sidebar
Click the Claude Dashboard icon in the Activity Bar.
3
Start exploring
Your projects, sessions, token usage, and estimated costs are automatically detected.
Contributions Welcome

Built in the open for people who live in Claude Code

If you care about better visibility into tokens, sessions, tools, prompts, and workflows, you can help shape where this dashboard goes next.

17 stars and 4 forks from developers following the project.

Report a bug
Found a parsing edge case, inaccurate metric, or UI regression? Open an issue and help us tighten the product.
Shape the roadmap
Suggest new insights, editor support, workflow ideas, or dashboard views that would help Claude Code users more.
Open a pull request
Fix bugs, improve UX, add docs, or ship features. Small polish and deep product work are both welcome.