Claude Code Lens (cc-lens)

Local analytics dashboard for Claude Code. No cloud, no telemetry, no API key, just your ~/.claude/ data, visualized.

npx cc-lens

The CLI finds a free local port, starts the dashboard, and opens it in your browser.

Quick Start

Run directly with npx:

npx cc-lens

On first run, cc-lens prepares a small runtime cache in ~/.cc-lens/. After that, launches are faster.

What You Can See

Overview

• Sessions, messages, token usage, estimated cost, and local storage.
• Trend cards with sparklines.
• Date presets for 7, 30, and 90 days, plus a custom date range picker.
• Usage over time, model distribution, peak hours, project activity, token breakdown, and recent sessions.

Projects

• Searchable, sortable project grid.
• Per-project cards with sessions, duration, estimated cost, languages, git branches, MCP/agent badges, and top tools.
• Project detail pages with sessions, cost over time, language distribution, branch activity, and tool usage.

Sessions

• Searchable session table with badges for compaction, agents, MCP, web search/fetch, and extended thinking.
• Full session replay reconstructed from JSONL.
• Assistant responses rendered as GitHub-flavored Markdown.
• Tool calls and tool results shown inline.
• File read/write/update tool results parsed into readable cards.
• Per-turn model, duration, token breakdown, and estimated cost.
• Compaction events shown in context with a token accumulation chart.

Costs

• Total estimated cost, cache savings, and estimated cost without cache.
• Cost over time and cost by project.
• Per-model token and cost breakdown.
• Cache efficiency panel.
• Pricing reference from lib/pricing.ts.

Tools & Features

• Tool ranking across all sessions.
• Tool categories for file I/O, shell, agents, web, planning, todos, skills, MCP, and other calls.
• MCP server usage details.
• Feature adoption across sessions.
• Tool error analysis.
• Claude Code version history.
• Git branch analytics.

Activity

• GitHub-style activity calendar.
• Current streak, longest streak, active days, and most active day.
• Usage over time, peak hours, and day-of-week patterns.
• Activity can be derived from session JSONL when the stats cache is incomplete.

Local Claude Code Files

• History: Search and page through ~/.claude/history.jsonl.
• Todos: Browse todos from ~/.claude/todos/ with search and status filters.
• Plans: Read saved plans from ~/.claude/plans/ with inline Markdown rendering.
• Memory: Browse and edit memory files across projects, with type filters and stale detection.
• Settings: Inspect ~/.claude/settings.json, installed skills, plugins, MCP servers, and storage usage.

Export & Import

• Export a portable .ccboard.json file containing stats, session metadata, facets, and recent command history.
• Preview export counts before downloading.
• Optionally filter exports by session start date.
• Drop an export file to preview an additive merge from another machine.

Import is intentionally preview-only right now. It shows which sessions are new or already present, but it does not write merged data back into ~/.claude/, to avoid corrupting live Claude Code files.

Navigation

• Global search: Cmd+K, Ctrl+K, or /.
• Session list keyboard navigation: j / k to move, Enter to open, Esc to clear.
• Page shortcuts: g plus a page key, for example g s for sessions, g p for projects, g c for costs.
• Responsive layout with desktop sidebar, collapsible navigation, mobile bottom nav, and mobile menu.
• Light and dark themes.

Multiple Claude Profiles

By default, cc-lens reads ~/.claude/. To point it at another Claude Code config directory, set CLAUDE_CONFIG_DIR:

# Default profile
npx cc-lens

# Work profile
CLAUDE_CONFIG_DIR=~/.claude-work npx cc-lens

On Windows PowerShell:

$env:CLAUDE_CONFIG_DIR="C:\Users\you\.claude-work"; npx cc-lens

The active config directory is shown in the CLI banner on launch.

Run From Source

Prerequisites

• Node.js 18+
• Claude Code with local data in ~/.claude/

Development

npm install
npm run dev

Open http://localhost:3000, or the port shown in your terminal.

Production Build

npm run build
npm start

Lint

npm run lint

Data Sources

cc-lens reads local Claude Code files directly:

• ~/.claude/projects/<slug>/*.jsonl: session JSONL and replay data
• ~/.claude/stats-cache.json: aggregate stats when available
• ~/.claude/usage-data/session-meta/: session metadata fallback
• ~/.claude/history.jsonl: command history
• ~/.claude/todos/: todo files
• ~/.claude/plans/: saved plan files
• ~/.claude/projects/*/memory/: project memory files
• ~/.claude/settings.json: settings, skills, plugins, and MCP config

Dashboard data refreshes every 5 seconds while the app is open.

Privacy

Claude Code Lens runs locally and reads files from your machine. It does not require a login, API key, hosted backend, or telemetry service. Your Claude Code history stays on your computer.

Cost Estimates

Claude Code stores token counts and model identifiers, not final billing totals. cc-lens estimates cost using the pricing table in lib/pricing.ts. If provider pricing changes, update that file to keep estimates current.

Star History