by JayantDevkar
Dashboard for monitoring claude code sessions.
# Add to your Claude Code skills
git clone https://github.com/JayantDevkar/claude-code-karmaGuides for using ai agents skills like claude-code-karma.
Last scanned: 5/30/2026
{
"issues": [],
"status": "PASSED",
"scannedAt": "2026-05-30T15:30:56.531Z",
"npmAuditRan": true,
"pipAuditRan": true
}claude-code-karma is an open-source ai agents skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by JayantDevkar. Dashboard for monitoring claude code sessions. It has 231 GitHub stars.
Yes. claude-code-karma passed SkillsLLM's automated security scan — a dependency vulnerability audit plus prompt-injection heuristics — with no high-severity issues. You can read the full report in the Security Report section on this page.
Clone the repository with "git clone https://github.com/JayantDevkar/claude-code-karma" and add it to your Claude Code skills directory (see the Installation section above).
claude-code-karma is primarily written in Python. It is open-source under JayantDevkar on GitHub, so you can review or fork the full source.
Yes. SkillsLLM lists many other AI Agents skills you can browse and compare side by side. Open the AI Agents category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh claude-code-karma against similar tools.
No comments yet. Be the first to share your thoughts!
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.
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.
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.
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.
Files — Every file operation in a sortable table — reads, writes, edits — with timestamps, actors, and the tools that made each change.
Subagents — Agents spawned during the session, grouped by type. Expand each to see message counts, tool calls, and what they were asked to do.
Skills — Skills invoked via /skill commands during the session, with their source plugin and invocation count.
Commands — Slash commands used during the session, showing built-in and plugin commands with usage counts.
Analytics — Per-session cost breakdown, token usage, cache hit rates, tool distribution with a donut chart, and a ranked list of every tool used.
See all your Claude Code workspaces organized by git repository. Each project card shows session count and when it was last active. Expand git repos to see individual project directories inside them.
Track your token usage, costs, velocity trends, cache hit rates, and coding rhythm across all projects. See which models you use most and how your usage patterns change over time.
See every tool Claude Code uses — built-in ones like Read, Edit, and Bash, plus any MCP integrations you've added. Grouped by server with call counts and session coverage. Switch to the Usage Analytics tab for activity trends and top tools over time.
Click into any tool for detailed stats — total calls, session count, main vs subagent split, usage trend over time, and a full session history.
Browse all your agents — built-in, custom, and plugin-provided. See total runs, token consumption, and filter by category to understand how your agent ecosystem is being used. The Usage Analytics view shows activity trends and your most-used agents.
Drill into any agent for run counts, token usage, average duration, usage trends, project breakdown, and a session history showing every time that agent was used.
Visualize all your Claude Code hooks organized by lifecycle phase — session start/end, tool use, agent lifecycle, and permissions. See which hooks can block execution and how many registrations each event has.
View all installed Claude Code plugins with their agents, skills, and commands. Filter between official and community plugins. See version info and when each was last updated.
Click into any plugin to see everything it provides — agents, skills, commands, MCP tools, and hooks — along with usage analytics showing activity trends and top-used components.
Track which skills are invoked across sessions, grouped by plugin or shown individually. Click into any skill for usage stats, context split (main vs subagent), and a full session history showing every time that skill was used.
Attach your Claude Code sessions to the tickets they were about. Karma stays read-only — it stores the link and caches the title/status, but never writes back to your ticket provider.
Three ways to link:
/link-ticket-to-session ABC-123 (or ask the agent in natural language) in any Claude Code session — uses your Linear / Atlassian / GitHub MCP server to fetch the titleSessionStart hook that watches for keys like feat/LINEAR-123-foo and links silently in the backgroundThen browse:
/tickets index showing every ticket touched, filterable by provider and projectclaude-karma/frontend/ also shows on the main claude-karma projectTickets Index — All linked tickets in a filterable table. Switch between All, Issues, and PRs on GitHub.
Filter by Provider — GitHub shows sub-pill filtering ([All N] [Issues N] [PRs N]) to toggle between categories.
Ticket Detail — View a ticket with all linked sessions. Cross-project rollup shows "N sessions · M projects" with tabs per project.
Project Tickets Tab — Every project page has a Tickets tab that aggregates across all git identity checkouts, so the same ticket appears even if linked from different branch directories.