CSI: Session Insights for Claude Code

See where your Claude Code time, tokens, and money actually go - organized by repo and branch.

Claude Code already saves every session to disk. This extension turns those raw transcripts into something you can actually use: a searchable, branch-organized history with accurate cost tracking and one-click resume - all running entirely on your machine.

Features

• Browse by branch - repo > branch > session, with per-branch rollups (sessions, token spend, files touched). The view nothing else gives you.
• Usage dashboard - cache-efficiency stat, token-split donut, and cost-over-time, by-model, and by-branch charts. No charting library, works offline.
• Accurate cost - uses LiteLLM's canonical pricing data and counts every token category (input, output, cache read, and cache writes), so totals track your real spend instead of undercounting.
• Full-text search - find that debugging session from last week across all projects.
• One-click resume - reopens a session in its correct working directory.
• Auto-index - new sessions are captured automatically once installed.

Private by design

Runs entirely on your machine. No account, no server, nothing uploaded. The index is a local SQLite file in ~/.claude-mem/. The only network call is an optional daily fetch of public model-pricing data (with an offline fallback).

Quick start

1. Install, then open the Claude Session Insights panel from the activity bar.
2. Approve the one-time capture hook prompt (auto-indexes future sessions).
3. Existing sessions backfill automatically. Open the dashboard from the toolbar graph icon.

Requirements

• VS Code 1.85+
• Claude Code with sessions stored under ~/.claude/projects/

Cost accuracy - what to expect

Costs are estimates computed from local token counts and current model prices, typically within about a dollar of your real spend. They count cache tokens, which are ~95% of a typical Claude Code bill. Provider support covers Anthropic, Bedrock, Vertex, and LiteLLM proxy setups. For the authoritative figure, use your LiteLLM spend logs or cloud invoice. If numbers ever look off (usually after a Claude Code version change), run Re-index.

License

MIT © 2026 AH Infotech LLC