Explore / claude-code-karma

JayantDevkar

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.

242 29 Python Apache-2.0updated 6 days ago

coding

View on GitHub Dispute this mapping →

Curator's take

Your ~/.claude directory is a goldmine Claude Code never shows you — Karma turns the JSONL into browsable sessions with full chronological timelines, cost and cache-hit breakdowns, subagent trees, and a surprisingly complete inventory of every plugin, skill, and hook you've installed with usage stats. Read-only ticket linking (Linear/Jira/GitHub) is the team-ready touch. Know the limits: Claude Code prunes session data after ~30 days, so history evaporates unless you keep Karma indexing; it's a two-process dev setup (FastAPI + SvelteKit), not a single binary; and it's Claude-only — no Codex/OpenCode. Pair with ai-token-monitor when all you want is the spend number next to your clock.

Mapped by ShipWithAI editors · links verified

README.md

Claude Code Karma

Your Claude Code sessions deserve more than a terminal.
A local-first, open-source dashboard that turns your ~/.claude/ data into a visual story — sessions, timelines, costs, and live activity, all on your machine.

Why Claude Code Karma?

If you use Claude Code, you already have a goldmine of data sitting in ~/.claude/ — every session, every tool call, every token. But it's all buried in JSONL files you'll never read.

Warning: Claude Code only keeps session data for about 30 days. Older JSONL files in ~/.claude/projects/ are automatically cleaned up. Since Karma reads directly from those files, deleted sessions will disappear from the dashboard too.

Claude Code Karma reads that local data and gives you a proper dashboard. No cloud. No accounts. No telemetry. Just your data, on your machine.

It works with both Claude Code CLI and Claude Desktop (Claude Code mode) sessions — any session that writes to ~/.claude/ shows up automatically.

Features

Session Browser

Browse all your Claude Code sessions in one place. Search by title, prompt, or slug. Filter by project. See live sessions at the top with real-time status badges.

Session Browser

Session Timeline & Overview

Dive into any session to see exactly what happened — every prompt, tool call, thinking block, and response laid out chronologically. The overview tab shows key stats like message count, duration, model used, and which tools were called.

Session Overview

Session Timeline

Session Detail Tabs

Each session page has dedicated tabs that break down different aspects of what happened during the session.

Tasks — See all tasks Claude created and completed during the session, displayed in a flow view with status tracking.

Session Tasks

Files — Every file operation in a sortable table — reads, writes, edits — with timestamps, actors, and the tools that made each change.

Session Files

Subagents — Agents spawned during the session, grouped by type. Expand each to see message counts, tool calls, and what they were asked to do.

Session Subagents

Skills — Skills invoked via /skill commands during the session, with their source plugin and invocation count.

Session Skills

Commands — Slash commands used during the session, showing built-in and plugin commands with usage counts.

Continue your stack

What teams reach for next — and why each earns a place beside claude-code-karma. Ranked by curator confidence.

Pairs well with

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 it fitsTwo halves of Claude Code observability over the same local data: Agent Flow is the live execution graph you watch while a session runs; Karma is the historical dashboard you consult afterwards — costs, timelines, tool and skill analytics.

Alternative to See all + compare →

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.

Why it fitsSame 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.

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 it fitsBoth read the session logs your coding CLI already writes, at opposite depths: ai-token-monitor is the glanceable menu-bar spend counter with plan-limit alerts; Karma is the full forensic dashboard — timelines, subagents, tools, tickets.