Quick answer
A Claude Code dashboard needs the two limit percentages with reset times, a daily token trend, a model split, and a session list sorted by cost. UsageAtlas builds those views from `~/.claude/projects` and shows 7, 30, or 90-day history. Local tracking needs no account.
The four panels
| Panel | Answers | Source |
|---|---|---|
| Limits | Can I keep working? | Reported windows |
| Trend | Is this a spike? | Daily token totals |
| Models | What is efficient? | Model field |
| Sessions | Which task cost most? | Session logs |
Set it up
- Download UsageAtlas and let it detect Claude Code.
- Confirm the history path; some installs use
~/.config/claude/projects. - Open Today for the windows.
- Open History and set 30 days.
- Set an alert at 20% remaining.
Know the boundaries
- Other machines appear only with sync or export.
- Deleted logs disappear from history.
- Cost is estimated unless the log records it.
- Provider billing remains the source of truth for money.
Four panels that matter
| Panel | Answers | Source |
|---|---|---|
| Session window | Can I keep working now? | Reported usage |
| Weekly cap | How much week is left? | Reported usage |
| Token history | What did the work cost? | Local logs |
| Model split | Where is the spend? | Session records |
A dashboard that shows only the percentage hides the decision. Pair the percentage with a reset timer and a token trend, then one glance tells you whether to start a refactor or wait.
UsageAtlas shows all four from local data, and the reset tracker covers keeping the timer visible.
Questions, answered
Does Claude Code have a built-in dashboard?
The CLI shows session usage and a cost command. It does not provide long-term charts or a model split.
Can I see Claude and Claude Code usage together?
The plan windows are shared. Local token history covers Claude Code logs, not chat messages in the apps.
Does the dashboard need my Anthropic login?
No for local logs. Connecting the provider for reported windows may require it.