I built a VS Code extension to see what Claude Code is actually doing across all my projects

If you use Claude Code heavily across multiple repos, you probably know this feeling.

You have Claude running in several projects at the same time and at some point you start wondering:

• How much did I spend this week?
• Which project burned the most tokens?
• What was that session from yesterday even about?

I kept hitting this problem, so I built a small tool for it.

It's a VS Code extension called Claude Code Dashboard that shows everything Claude Code has been doing across your projects in one place.

Main features:

• 🗂️ See all Claude Code projects in one sidebar
• 📝 Session history per project (shows the first prompt as preview)
• 💰 Token and cost breakdown per session and per project
• 📁 See which files Claude touched and which tools it used
• ⚡ Detects when a Claude session is actively running

The nice part: there’s no setup.

No API keys, no accounts, nothing external.

It just reads the session data Claude Code already stores locally.

I mainly built it because once you start using Claude Code a lot, you lose visibility pretty quickly.

Available here:

Promo Homepage: https://claude-code-dashboard-jspw.vercel.app

VS Code Marketplace: https://marketplace.visualstudio.com/items?itemName=jspw.claude-code-dashboard

Open VSX (Cursor / Windsurf) -> https://open-vsx.org/extension/jspw/claude-code-dashboard

Source Code -> https://github.com/jspw/Claude-Code-Dashboard

It's free and open source (AGPL-3.0).

If you're a heavy Claude Code user, I'm curious if this would actually be useful for you or if there are other things you'd want to see in a dashboard like this.

Comments

[Henry Godnick]

Nice work on this. The "which project burned the most tokens" question is exactly the one I keep asking myself. The per-session breakdown is really useful for post-hoc analysis.

One thing I've found complements a tool like this is having something that shows usage while the session is running, not just after. I keep a real-time token counter visible in my macOS menu bar so I can catch a runaway session before it eats through my budget. The combo of live awareness during work + detailed history after is pretty powerful for staying on top of costs.