Unclear Whether any report in Claude Code produces or shows these recommendations yet is not known.
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
recommendationslist (key, pct, title, detail) and an optionalfixobject holdingkeysandmessages. The olderagents,skills,pluginsandmcp_serverslists 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
/effortcommands 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/usagemeasured 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.
Names in the bundle/effort
/effort
Claude Code changelog modified, high confidence
* Fixed `/effort status`, `/effort ultracode` and the prompt's effort indicator showing a guessed effort level when `CLAUDE_CODE_EFFORT_LEVEL` is `auto` or `unset` and no level is sentsee the edit
/effort
overview modified, high confidence
| [Effort](https://platform.claude.com/docs/en/build-with-claude/effort) | Control how many tokens Claude uses when responding with the effort parameter, trading off between response thoroughness and token efficiency. | ZDR eligible | <Pla…see the edit
/effort
Run Claude Code programmatically modified, high confidence
> * `/model`, `/effort`, `/fast`, `/color`, and `/rename` accept the value as an argument, for example `/model sonnet`, and `/mcp` with no argument prints a text summary of server status. These forms follow each command's [availability not…see the edit
/effort
What's new modified, high confidence
**Claude Opus 4.8**: the new default model for Max, Team Premium, Enterprise pay-as-you-go, and Anthropic API accounts, with high effort by default and `/effort xhigh` for the hardest tasks.see the edit
/effort
Manage multiple agents with agent view modified, high confidence
* `/model`, `/effort`, and `/fast` set [what the sessions you dispatch next start with](#set-the-model-effort-and-fast-mode). `/effort` and `/fast` require Claude Code v2.1.299 or later.see the edit
/effort
Models overview modified, medium confidence
Each model's `capabilities` object also includes `thinking.types.between_tools`, which reports whether the model accepts `thinking: {type: "between_tools"}`, the setting that [turns off up-front thinking](https://platform.claude.com/docs/e…see the edit
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 since
A small documentation edit on prompting-claude-opus-5 touched a line naming /effort after this was published.
* **Efficiency at lower effort:** `low` and `medium` [effort](https://platform.claude.com/docs/en/build-with-claude/effort) produce strong quality at a fraction of the tokens and latency of higher settings. Start with the default (`high`) …build-with-claude/prompt-engineering/prompting-claude-opus-5 see the edit
Confirmed since
Anthropic's documentation has since written up /effort, on customer-support-chat.
For customer support chat, Claude Opus 5.5 is well suited to balance intelligence, latency, and cost, including the most complex support scenarios that require deep reasoning across long, multistep conversations. However, for instances whe…about-claude/use-case-guides/customer-support-chat see the edit
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
Whether any report in Claude Code produces or shows these recommendations yet is not known.
Anthropic's documentation agrees
/effort on Claude Code changelog
Anthropic's release notes agree
Fixed /effort and /autocompact settings not applying when the model name differed from a modelOverrides value by letter case or a [1m] tag