You'll noticeTier: how much it should matter to you
5Useful: my rating, 1 to 5
5Signal: worth watching, 1 to 5
Usage ReportArea: what it touches
In DevelopmentKind: in v2.1.305,
What probably matters to youSection of the release
Unclear It is not clear where in /usage the suggestions and the choice of fixes appear.
What
/usage shows session cost, plan limits and activity. It now looks through your local transcripts over a 24-hour window and a 7-day window and works out which habits cost the most. The work runs only when the server-controlled switch tengu_tidy_abacus allows it; that switch falls back to on when the server sends nothing.
Behaviours it measures include max effort, workflow agents, always-on context (memory, skills, MCP servers, agents), large tool results, cache misses, long context, subagents, skills, plugins and MCP servers.
It turns them into ranked suggestions, for example "Switch from max to ... effort", "Compact before you step away" (/compact), "Start fresh when you switch tasks" (/clear), "See what fills your context" (/context) and "Trim ...".
The summary text now lists these server-provided recommendations, each as a percentage, a title and an optional detail. It used to list behaviours above a fixed percentage.
The usage report schema gains the optional recommendations list (key, pct, title, detail) and an optional fix object holding keys and messages. The older agents, skills, plugins and mcp_servers lists stay.
A fix is sent as one or more of your own messages, queued at a low priority to run after the current work, with any /effort commands first. The fix prompt begins "Fix what /usage flagged. Show me each change before you make it."
A review prompt can gain a section, ## Check 10 — what /usage flagged, listing what /usage measured from the last 7 days of local sessions and asking the model to report each item with its share. It is empty unless several conditions hold.
Why
/usage moves from a plain report to advice you can act on, and a chosen fix asks Claude to show each change before making it.
Nothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.
This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.305: on
These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Added sinceA small documentation edit on overview touched a line naming /usage after this was published.You can view your rate limits under [Rate limits in the Claude Console](https://platform.claude.com/usage/limits) and your spend limits on the Console's [Billing](https://platform.claude.com/settings/billing) page. For higher rate limits o…api/overviewsee the edit
Confirmed sinceAnthropic's documentation has since written up /usage, on web-search-tool.To protect shared capacity, the Batches API throttles web search requests for each organization, so large batches with many searches might take longer to complete. You can see your organization's web search rate limit on the [Rate limits](…agents-and-tools/tool-use/web-search-toolsee the edit
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtIt is not clear where in `/usage` the suggestions and the choice of fixes appear.
Anthropic's documentation agreesAnthropic's documentation has since written up /usage, on web-search-tool.
Anthropic's release notes agreeFixed /usage rows being cut off in narrow terminals
The name it cites is new in this buildNew in this build: tengu_tidy_abacus
