
<h1 id="claude-usage">Claude Usage <span style="display:inline-flex;align-items:center;vertical-align:middle;padding:2px 10px;font-size:14px;font-weight:700;border-radius:9999px;background:linear-gradient(135deg,#6366f1,#8b5cf6);color:white;letter-spacing:0.05em;position:relative;top:-2px;margin-left:6px;">PRO</span></h1>

Claude Usage turns your Claude Code history into clear graphs, so you can see how your token usage changes over time and which projects are actually burning those tokens.

## Beautiful Usage Graphs

The main Claude page gives you a time-based view of usage for the selected period. You can inspect total tokens, cost, input versus output tokens, cache reads, cache writes, and an active session card with live burn-rate data when Claude is currently running.

Instead of dropping you into raw numbers, DevKeepr presents the data visually so usage patterns are obvious at a glance.

![Claude Usage graphs and project breakdown](/screenshots/docs/claude-usage.webp)

## See Which Projects Burn The Most

DevKeepr does not stop at total usage. It also breaks your Claude usage down per project, so you can quickly see where your spend is actually going.

The main usage page shows your top projects for the selected period. You can select projects from that list and overlay them on the chart, which makes it easy to compare a specific project against your total token usage over time.

## Drill Into A Single Project

Each project also gets its own Claude Usage widget on the project detail page.

That view shows the project's tokens, cost, and percentage of your total Claude usage for the selected period. It also includes a dedicated chart for the project, with an option to compare the project's usage line against your overall total usage.

## Polyscope Worktrees Still Count Toward The Right Project

DevKeepr takes extra care with [Polyscope](https://getpolyscope.com) clones. Even though those worktrees live outside your main project directory, their Claude usage is still mapped back to the parent project.

That means usage from temporary review branches, parallel workspaces, and other Polyscope-driven work still rolls up into the project it belongs to, instead of fragmenting your stats across random clone paths.

## Keep The Big Picture And The Details

Claude Usage gives you both the high-level trend and the project-level drilldown. You can watch your overall token usage over time, then zoom in on the exact projects responsible for it.

If you are trying to understand where Claude is most valuable, where costs are climbing, or which project is consuming the most attention, this page gives you that answer quickly.
