Usage Reader · Local Client-Side Session Reader · Free Tool
Why your weekly coding limit ran out early
When you hit your weekly session limit early, totals by day or model do not tell you what caused it. Usage Reader inspects your local session logs on your own machine, never uploads a byte, and prints one page naming your five biggest weekly drains and the single change that saves the most.
What it measures locally (zero network upload)
Every number is computed inside your browser or local terminal from your own session files, and every finding points back to the exact session lines that caused it.
Five causes it separates
- Windows that grew fat. Every turn re-sends the whole conversation context; Usage Reader shows where a fresh session would have cut the cost.
- Wakes that changed nothing. Turns started by a timer or notification that ended with no file edit and no output.
- Repeated file reads. The same file read again and again within one sitting instead of reading the line range needed.
- Fan-out subagents. Background helpers spawned beside the main window and what share of the weekly budget they consumed.
- Long-running retry loops. Repeated failing commands or build outputs re-fed into the window.