Most Claude Code tools are CLI cost-counters. Claude Session Monitor is different: a native VS Code extension that turns your local session files into a browsable workspace — full transcript, tool calls & sub-agents, per-response token & cost, an analytics dashboard, and a CLAUDE.md memory view. Everything is searchable, resumable, and 100% local-first — nothing leaves your machine. Free; works in VS Code, Cursor & VSCodium.
No reviews yetBe the first to leave a review for Claude session monitor
Hunter
📌
If you use Claude Code, every session is saved as a JSONL file under ~/.claude/projects/ — but there's no good way to look back at them. I kept losing track of what I did, what a session cost, and which conversation had that one fix I needed.
Claude Session Monitor is a VS Code extension that turns those files into a fast, native workspace:
• 📂 Sessions sidebar — grouped by repo → branch, with search, favorites & scope
• 🔍 Session detail — full transcript, tool calls, sub-agents, per-response token & cost breakdown
• 📊 Analytics dashboard — cost, token trends, tool distribution, activity heatmap
• 🧠 Memory view — your global & per-project CLAUDE.md and memory files, one click to open
• ▶️ Resume / rename / star / delete any session, right from the sidebar
Report
The transcript search is shockingly fast and the per-response cost breakdown actually helped me catch a runaway loop in one of my sessions. Glad it stays local.
Report
Hunter
@berivan24061 Thank you — Catching a runaway loop from the per-response cost is exactly why that breakdown exists: one response quietly ballooning is almost invisible in a terminal. And yes, local-first is non-negotiable — your session content never leaves your machine. If anything ever feels slow or looks off, I'd love to hear it!
The transcript search is shockingly fast and the per-response cost breakdown actually helped me catch a runaway loop in one of my sessions. Glad it stays local.
@berivan24061 Thank you — Catching a runaway loop from the per-response cost is exactly why that breakdown exists: one response quietly ballooning is almost invisible in a terminal. And yes, local-first is non-negotiable — your session content never leaves your machine. If anything ever feels slow or looks off, I'd love to hear it!