What
If your organization has set a default effort level for the current model, /effort output ends with , set by your organization and the effort picker shows a note explaining it. When no org default exists, nothing extra appears.
Details
- The note reads from an org-configured effort value for the resolved model.
Evidence
Your organization's default effort for this model is
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Names in the bundle/effort
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 Orchestrate subagents at scale with dynamic workflows touched a line naming /effort after this was published.
`/effort ultracode` lasts for the current session; to have every session start with it, set the [`ultracode`](/docs/en/settings-reference#ultracode) setting. Drop back with `/effort high` when you return to routine work. The `/effort` menu…workflows see the edit
Confirmed since
Anthropic's documentation has since written up /effort, on All settings.
Cap the [effort level](/docs/en/model-config#adjust-effort-level) a session can use, leaving lower levels available. Any higher level runs at the cap instead, including one from `/effort`, the `/model` picker, `--effort`, [`CLAUDE_CODE_EFF…settings-reference see the edit
Two sources agreeTwo things we can check say the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up /effort, on All settings.
Anthropic's release notes agree
Changed /effort to save your default effort level per model, so each model keeps its own setting when you switch