Cc-Lens, Open Source Analytics Dashboard for Claude Code
Direct ~/.claude/ parsing with session replay beats generic AI usage trackers.
See and manage your entire Claude Code config in one place
Consolidates Claude Code's 13 fragmented config surfaces into one searchable dashboard.
Claude Code users managing complex configurations across multiple projects
Claude Code config is spread across 13 surfaces and 4 scope levels. Keeping track of what's actually configured — and where — means hunting through a half-dozen directories.
Lens scans everything in one go: see effective values merged across scopes, or break it down file-by-file. Edit, add, enable/disable entries inline. Switch between repos from the sidebar. Import config from another project when starting something new. `⌘K` to search across all surfaces and workspaces at once.
Install it as a Claude Code plugin:
``` /plugins add-marketplace github:ugudlado/lens /plugins install lens@ugudlado /lens:open ```
Contributions, ideas, and issues welcome — code is open for everyone.
Direct ~/.claude/ parsing with session replay beats generic AI usage trackers.
Service link dashboard with health checks beats scattered Confluence bookmarks cleanly.
Hook-based capture beats OTEL for Claude Code agent visibility.
Three-tier instruction hierarchy beats monolithic prompts, but only for Claude Code users.
Runs extraction and search server-side so your local MCP is a tiny HTTP client — no local DBs, no giant RAM leaks, and an easy npx install and .mcp.json or global MCP registration. It exposes clear tools (save_memory, recall_memories, extract_memories, get_project_context) and adds project-scoped + global preferences — a pragmatic fix for Claude Code's tiny flat-file memory. The tradeoff is obvious: usefulness depends on the hosted API (privacy, uptime, cost), and the repo looks early-stage with minimal commits and docs beyond the quickstart.
Brewfile alternative with TUI picker, but dev setup tools are crowded.