BrowseFull catalogOutcomesSolve a specific problemRolesStack by teamTrustFilter by risk tier
← Back to the Claude Observatory

cc-lens

Skill Development Solid
Works inClaude Code
Solid Scanned — metadata only

Claude Code usage is otherwise opaque. cc-lens turns your local ~/.claude/ data into a dashboard showing where sessions, tokens, and spend actually go — usef…

Local analytics dashboard for Claude Code that visualizes the data already in your ~/.claude/ directory — no cloud, no telemetry, no API key. Run npx cc-lens to see sessions, token usage, estimated costs and cache savings, project trends, tool and MCP rankings, activity calendars, and full session replay of JSONL conversations.

576 starsMIT (commercial OK)FreeQuick setup

Claude Code usage is otherwise opaque. cc-lens turns your local ~/.claude/ data into a dashboard showing where sessions, tokens, and spend actually go — useful for spotting cache and model savings and for gauging team adoption — without sending anything to the cloud.

Developers debugging Claude Code behavior or teams evaluating Claude Code adoption who want visibility into session activity.

Claude Code Claude Cowork Claude Chat

https://github.com/Arindam200/cc-lens

By Arindam200

How to Get It

Option 1: Claude Desktop App (Code Mode)Click the + button next to the prompt box → PluginsAdd plugin. Search and click Install. Skills work in Claude Code only.
Option 2: Paste into Claude CodeCopy the command below and paste it into your conversation. Claude will install it.
Command
npx cc-lens

Tip: Paste this into a Claude Code conversation. Verify command matches your Claude Code version.

First thing to try

After installing, paste this into Claude:

Help me monitor Claude Code session activity in a real-time dashboard
CostFree

Trust Signals Auto-scanned

Stars576Contributors2Last updated2026-06-27LicenseMIT (OK for commercial use)Known CVEsNone foundSources: GitHub Advisory Database + OSV.dev · Scanned 2026-08-02 · scanner v1

Community Pulse Active

Discussed on Hacker News, Reddit

3 mentions across 2 sources

Reviewer notes

Auto-scanned review. These are observations, not a security certification.

catalog_hygiene stale-eval refresh: Scored from trust signals (evidence-eval-v1): 556 GitHub stars; 1 contributors; last commit 9d ago; license MIT.

Things to check

  • Reads local ~/.claude/ data only; costs are estimates based on pricing references. Import of exported .cclens.json files is preview-only — it does not write merged data back into ~/.claude/. Point it at other profiles with CLAUDE_CONFIG_DIR.

How to evaluate tools before deploying →

Data shown here comes from public APIs and automated scanning. Reviewer notes reflect one person's experience. This is not a security certification or legal recommendation. Always evaluate tools according to your own organization's policies.

Evaluation

Ease of Use
4/5
Versatility
4/5
Reliability
3/5
Security
3/5
Overall score3.60 / 5.00 SolidEvaluatedJul 2026
catalog_hygiene stale-eval refresh: Scored from trust signals (evidence-eval-v1): 556 GitHub stars; 1 contributors; last commit 9d ago; license MIT.

← Back to the Claude Observatory

Rolling Claude out in your org? Let's talk.

Start a conversation →