Everything Claude Code keeps in ~/.claude: every conversation, every token, every skill
and MCP server, in one local dashboard that runs entirely on your machine.
$ curl -fsSL https://my-claude.pages.dev/install.sh | bash
Real screenshots, not mockups. This is what opens at 127.0.0.1:8766.

Skills, conversations, 30-day tokens, spend and disk, pulled straight from your local files the moment you open it.

Every token and dollar, broken down the way you actually think about it, with the caching wins made visible.

Every session you have ever had, searchable in full text and ready to reopen, right down to what each one cost.

Every skill rendered readable, with the usage data that tells you which ones earn their place and which you forgot.

All your MCP servers and plugins in one place, including the per-project ones you set up months ago and forgot.
Paste the install command into your terminal. It sets everything up for you, with no manual steps.
curl … install.sh | bashMy Claude reads your skills, MCP servers, plugins, usage logs and transcripts, all on your machine.
indexing ~/.claude …Your browser opens the dashboard once the server is ready, bound strictly to loopback. Only you can reach it.
127.0.0.1:8766My Claude reads your ~/.claude and serves the dashboard on 127.0.0.1. Your transcripts, prompts and costs are computed on your machine and are never uploaded.
Two things do go out, both of them yours and both visible in the source. A skill you explicitly choose to push to your own GitHub. And, while the Usage page is open, one request to api.anthropic.com/api/oauth/usage — authorised with the Claude Code token already in your keychain — so the page can show your real plan limits. That request carries the token and nothing else; decline the keychain prompt and the page falls back to the copy Claude Code cached locally.
Free and open source. One command, about twenty seconds, entirely on your machine.
$ curl -fsSL https://my-claude.pages.dev/install.sh | bash