[DOCS] `/usage` documentation omits large session files in limits breakdown
Documentation Type
Incorrect/outdated documentation
Documentation Location
https://code.claude.com/docs/en/costs
Section/Topic
Using the /usage command
Current Documentation
The docs currently say:
On a Pro, Max, Team, or Enterprise plan,/usagealso shows a breakdown of what counts against your plan limits. It attributes recent usage to skills, subagents, plugins, and individual MCP servers, with each shown as a percentage of the total. Pressdorwto switch between the last 24 hours and the last 7 days. The figures are approximate and computed from local session history on this machine, so usage from other devices or claude.ai is not included.
But the v2.1.152 changelog says:
The /usage breakdown now includes large session files; files are scanned with a streaming read so memory usage stays flat
What's Wrong or Missing?
The current /usage documentation still describes the limits breakdown as if it only covers skills, subagents, plugins, and individual MCP servers.
That is outdated for v2.1.152. The changelog says the breakdown now also includes large session files, but the main /usage docs do not mention that additional contributor anywhere.
The docs also do not mention the user-visible behavior change that large session files are scanned with a streaming read so memory usage stays flat while computing the breakdown.
Suggested Improvement
Update the /usage section in https://code.claude.com/docs/en/costs to reflect the v2.1.152 behavior.
At minimum:
- Add large session files to the documented list of contributors in the limits breakdown.
- Clarify that Claude Code now scans those files with a streaming read when building the breakdown.
- Note that this keeps memory usage flat when users have very large local session files.
Impact
Medium - Makes feature difficult to understand
Additional Context
Affected Pages:
| Page | Context |
|------|---------|
| https://code.claude.com/docs/en/costs | Main /usage documentation lists breakdown contributors but does not mention large session files or the streaming-read behavior added in v2.1.152 |
Total scope: 1 page affected
This gap is based on the v2.1.152 changelog entry for /usage.
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗