# claude-dashboard

> Local web page that tracks all your Claude Code sessions, diffs and costs

- Repository: https://github.com/JonImmsWordpressDev/claude-dashboard
- Category: Coding agents & dev tools
- Stars: 24 · Forks: 6 · Language: JavaScript · License: MIT
- Experience: Beginner friendly
- Page: https://ir.adyog.com/repos/jonimmswordpressdev/claude-dashboard/

Once you have a few Claude Code sessions open, it is hard to tell which one is waiting for an answer, what it changed, or what the week has cost. This project is a small Node.js server that reads the session files in ~/.claude and shows the answers on one page, updated live.

It is read-only. It never writes to Claude's files, has no npm dependencies, needs no API keys, and listens only on 127.0.0.1. The one outside call is optional: it asks Anthropic's usage API for your quota meters, using the sign-in Claude Code already has.

Instead of switching between terminals, you watch a departures-style board. A waiting session turns amber and shows its question or the command awaiting permission. You can open any transcript, read a diff of the files a session edited, or resume it in the right folder.

## What it does

- **Live session board**: Every running claude session is a row. A waiting session turns amber and shows the question, the command awaiting permission, or Claude's last line. macOS notifications and an idle reminder are included.
- **Diffs of what Claude changed**: A changes panel lists the files a session edited, with added and removed lines and a unified diff. It is built from the pre-edit backups Claude Code keeps. Nothing is reverted.
- **Transcripts and search**: Read any past or running session, with live following. Search every prompt you have sent, filter by project or date, and export a transcript as markdown.
- **Cost and usage stats**: Estimated spend per project, model and week, computed from the tokens in your transcripts. You can set a weekly budget and get alerts at 75, 90 and 100 percent.
- **Plugins and MCP inventory**: Lists installed plugins and MCP servers with their on/off state, scope, stale flags and whether they need auth. Project details show CLAUDE.md, memory files and settings.

## What you could build

- Watch several Claude Code terminals at once and jump to whichever one is waiting for you.
- Review the diff of every file a session touched before you commit it.
- Track how much each project and model costs per week against a budget.
- Resume an old session in the right folder with one click.
- Audit which plugins, MCP servers and projects are missing instructions or memory.

## Who it's for

Anyone who runs Claude Code in more than one terminal on macOS or Linux; you need Node.js 18 or newer and an existing Claude Code setup.

## Get started

Run the npx command to start the server and open the dashboard in your browser. To keep it always on, clone the repo and run ./install.sh, then visit http://127.0.0.1:4517.

```
npx claude-mission-control
```
```
./install.sh
```
```
node server.js
```

Tags: claude-code, dashboard, developer-tools, cost-tracking, nodejs