StackMap
Subscribe
Explore / cc-lens
Arindam200

cc-lens

npx cc-lens: local analytics dashboard over ~/.claude — sessions with replay, cost and cache breakdowns, insights and budgets, team-adoption mode, a yearly Wrapped card. No cloud, no telemetry.

568 76 TypeScript MITupdated 19 days ago
coding
View on GitHubDispute this mapping →
Curator's take

The zero-friction option among Claude Code dashboards: one npx command, loopback-bound by default, and v0.4's Insights tab actually recommends actions — cache, model choice, compaction, plan-fit and budget opportunities mined from your own usage — instead of just charting it. Team mode (shared-folder push hub + terminal digest) is a real differentiator for leads tracking adoption. Costs are estimates from a local pricing table (`~/.cc-lens/pricing.json` to override) — treat them as directional and keep the table current. Claude-only; for subagent forensics and ticket linking, claude-code-karma digs deeper; for a number next to your clock, ai-token-monitor.

Mapped by ShipWithAI editors · links verified
README.md

cc-lens CLI

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.

[!NOTE] cc-lens 0.4.0 is out

Adds Insights, budgets, team adoption, terminal digest, Wrapped, and expanded project docs.

View the v0.4.0 release notes

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

Dashboard overview
Track sessions, messages, tokens, cost, storage, trends, models, peak hours, projects, and recent activity.

Sessions

Session replay and chat
Search sessions, replay JSONL conversations, inspect Markdown replies, tool calls, costs, tokens, and compactions.

Costs

Costs
Review estimated spend, cache savings, project costs, model breakdowns, token usage, and pricing references.

Insights

Insights
Find cache, model, compaction, plan-fit, budget, and savings opportunities from local usage patterns.

Projects

Projects
Browse projects by sessions, duration, spend, languages, branches, MCP usage, agents, and top tools.

Project Trends

Project trends
Analyze project sessions, spend, language mix, branch activity, model usage, tools, and activity over time.

Tools & Features

Tools and features
Compare tool rankings, categories, skill (slash-command) usage, MCP servers, feature adoption, errors, versions, and git branch usage.

Activity

Activity calendar
View activity calendars, streaks, active days, peak hours, day-of-week patterns, and usage consistency.

Tasks

Tasks
Browse Claude Code todos with search, status filters, task metadata, project context, and local file provenance.

Workspace

Workspace
Inspect workspace state, memory, settings, installed skills, plugins, MCP servers, and local storage usage.

Wrapped

Wrapped
Create a yearly card with sessions, usage, spend, favorite tools, active projects, and local highlights.

Export & Import

Export
Export portable .cclens.json files with stats, metadata, facets, history, previews, and date filters.

Import is 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.

Multiple Claude Profiles

By default, cc-lens reads ~/.claude/. To point it at another Claude Code con

Continue your stack

What teams reach for next — and why each earns a place beside cc-lens. Ranked by curator confidence.