context-attachment-manager
Codex and Claude Code plugin (works in Claude Desktop): choose which past images go to the model with your next message. Unchecked images become placeholders, the conversation goes on, and requests st
See exactly what Claude is doing — token usage, estimated costs, sessions, and insights across all your projects, right inside VS Code. Free, open source, fully local.
PluginsTypeScript · JavaScriptGitHub @jspwOnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
A VS Code extension that shows you exactly what Claude is doing — tokens, costs, sessions, and insights across all your projects, right inside VS Code.
Taken from the repository README
Loading the full README. The saved excerpt is shown below.
A VS Code extension that shows you what Claude is doing on your machine — token usage, estimated costs, sessions, and insights across all your projects, right inside VS Code.
No API key required. No data leaves your machine.
Main dashboard — projects, stats, weekly recap, and estimated cost overview
Charts tab — 30-day token trend, usage by project, projected monthly estimated cost
Insights tab — heatmap, tool usage, productivity by hour, hot files
Project detail — session history with prompt previews and token breakdownRead the full README ↗A VS Code extension that shows you what Claude is doing on your machine — token usage, estimated costs, sessions, and insights across all your projects, right inside VS Code.
No API key required. No data leaves your machine.
Main dashboard — projects, stats, weekly recap, and estimated cost overview
Charts tab — 30-day token trend, usage by project, projected monthly estimated cost
Insights tab — heatmap, tool usage, productivity by hour, hot files
Project detail — session history with prompt previews and token breakdown
Search for Claude Code Dashboard in the VS Code Extensions panel, or install directly:
Requirements: VS Code 1.85+ and Claude Code installed and used at least once.
~/.claude/settings.json; a backup is made first). Choose Enable, Not now, or Never — your choice is remembered and the dialog never re-asks.Skipping hooks is fine — the dashboard still shows all historical data. You only lose the live "Claude is running" indicator. Toggle later anytime with Claude Code Dashboard: Enable Live Tracking / Disable Live Tracking in the command palette. Uninstalling the extension automatically removes the hooks and event file.
| Tab | What you see |
|---|---|
| Overview | Weekly recap, today's tokens & estimated cost, active sessions, full project list |
| Charts | 30-day token trend, usage by project, projected monthly estimated cost |
| Insights | Usage heatmap, tool breakdown, productivity by hour, hot files |
Project detail view — click any project to see its full session history, turn-by-turn conversation, token breakdown, estimated cost, files touched, CLAUDE.md, and MCP servers. Export to JSON or CSV any time.
~/.claude/projects/.totalTokens exclude cache-read tokens, which Claude may reuse heavily across long sessions.est.* in the UI.Search for Claude Code Dashboard in VS Code settings (Cmd+, / Ctrl+,).
| Setting | Default | Description |
|---|---|---|
claudeDashboard.monthlyTokenBudget | 0 | Monthly token cap. Set to 0 to disable. |
claudeDashboard.monthlyBudgetUsd | 0 | Monthly estimated cost cap in USD. Alerts at 80% and 100%. Set to 0 to disable. |
No projects showing
— Verify ~/.claude/projects/ exists, then run Claude Code Dashboard: Refresh from the command palette. Check the Output panel (select "Claude Code Dashboard") for errors.
Sessions not updating in real time
— Run Claude Code Dashboard: Enable Live Tracking from the command palette, then check ~/.claude/settings.json for entries referencing .dashboard-events.jsonl. The file watcher fallback still updates within ~300ms.
Cost numbers look off
— Cost is estimated locally from parsed token usage, detected model family, and a static pricing table. Cache read tokens are tracked separately and excluded from totalTokens, but still contribute to estimated cost.
Corrupted settings.json after hook injection
— Restore the backup: cp ~/.claude/settings.json.bak ~/.claude/settings.json
The extension only reads files in ~/.claude/ and your project directories. No network requests. No telemetry. The only files it ever writes are:
~/.claude/settings.json — hook config (with your consent; backup made first)~/.claude/.dashboard-events.jsonl — live events from the injected hooks~/.claude/.dashboard-live — marker file that arms the hooks (deleting it disables them instantly)~/.claude/settings.json.bak — backup before hook injection or removalDisabling live tracking (or uninstalling the extension) removes the hooks, the marker, and the event file.
Contributions are welcome! Please read the Contributing guide before opening a PR.
See SECURITY.md for how to report vulnerabilities privately.
See CHANGELOG.md for the full version history.
AGPL-3.0 — free to use and modify, but any modified version must also be released under the same license. Commercial reselling is not permitted.