StackMap
Subscribe

cc-lens alternatives

Curated alternatives to cc-lens — and why you'd switch.

claude-code-karma

Local-first dashboard over ~/.claude — sessions, timelines, per-session costs, tool/agent/skill/plugin analytics, live activity via hooks, and ticket linking. No cloud, no telemetry.

Why switchSame job — a local dashboard over ~/.claude JSONL. cc-lens is the one-command npx tool with insights, budgets and team adoption; Karma is the two-process forensic suite with subagent trees, hook/plugin inventories and Linear/Jira/GitHub ticket linking.
Full comparison →
agent-flow

Live node-graph visualization of Claude Code and Codex sessions — watch agents think, branch into subagents and call tools in real time. VS Code extension or npx web app. Apache-2.0.

Why switchBoth watch coding-agent sessions, in different tenses: agent-flow draws the live node graph while the agent thinks and branches, cc-lens is the after-the-fact dashboard — replay, cost and cache breakdown.
Full comparison →
abtop

htop for AI coding agents: every Claude Code, Codex and OpenCode session in one TUI — tokens, context-window %, rate limits, child processes, orphan ports. Read-only, no API keys. Rust.

Why switchLive vs retrospective: abtop shows what your agents are doing right now; cc-lens analyzes what they did — replays, cost/cache breakdowns, budgets. Many desks end up running both.
Full comparison →
agentacct

Local-first work receipts for coding agents: reads the session logs Claude Code, Codex, OpenCode and Hermes already write and reports what each task did, what it cost, and whether a check proved it.

Why switchcc-lens is analytics over ~/.claude: session replay, cache and cost breakdowns, budgets, team adoption. Agentacct is cross-harness and receipt-shaped, built around a lifecycle that separates what the agent claimed from what was proven. Dashboard versus audit record.
Full comparison →
ai-token-monitor

Menu-bar/tray app for macOS and Windows that reads Claude Code, Codex and OpenCode session logs and shows live token spend — per-model pricing with cache reads, plan-limit bars, webhook alerts.

Why switchBoth read local session logs to answer 'what is Claude Code costing me' — ai-token-monitor as a glanceable menu-bar counter with plan-limit alerts, cc-lens as a full browser dashboard with history, insights and budgets.
Full comparison →
codeburn

Local-first cost ledger for AI coding: reads the session files 36 tools already write and breaks every token and dollar down by task, model, project. TUI, web, desktop, menubar — no proxy, no keys.

Why switchBoth mine local session files, opposite depth-vs-breadth bets: cc-lens is Claude-only forensics — replay, cache and cost breakdowns over ~/.claude; CodeBurn is the cross-tool ledger unifying 36 tools into one spend view.
Full comparison →