Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [DOCS] Commands reference shows outdated `/effort` no-argument behavior [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#49286•Fetched 2026-04-17 08:45:33
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
0
Author
coygeekcoygeek
Participants
coygeekcoygeek
Timeline (top)
labeled ×3
RAW_BUFFERClick to expand / collapse

Documentation Type

Incorrect/outdated documentation

Documentation Location

https://code.claude.com/docs/en/commands

Section/Topic

/effort slash command behavior when run without arguments

Current Documentation

The docs currently say:

/effort [low|medium|high|max|auto] — Set the model effort level. low, medium, and high persist across sessions. max applies to the current session only and requires Opus 4.6. auto resets to the model default. Without an argument, shows the current level. Takes effect immediately without waiting for the current response to finish

The effort configuration page also says:

/effort: run /effort low, /effort medium, /effort high, or /effort max to change the level, or /effort auto to reset to the model default

In /model: use left/right arrow keys to adjust the effort slider when selecting a model

What's Wrong or Missing?

Changelog v2.1.111 says /effort now opens an interactive slider when called without arguments, with arrow-key navigation between levels and Enter to confirm.

The current docs are outdated in two ways:

A. The command reference describes the old no-argument behavior

It still says /effort without an argument only shows the current level.

B. The interactive picker behavior is only documented under /model

The docs describe slider-based effort selection for /model, but do not explain that /effort now also opens an interactive picker when invoked without an argument.

Suggested Improvement

Update the /effort entry in the commands reference and the effort configuration docs to reflect the new behavior.

Suggested wording:

Running /effort without an argument opens an interactive effort slider/picker. Use the arrow keys to move between effort levels and press Enter to confirm.

It would also help to clarify the difference between:

  • /effort with no argument → opens the interactive picker
  • /effort low|medium|high|max|auto → applies the specified value directly

Consider adding a short cross-reference to the relevant keyboard navigation page if the picker uses the standard select/model-picker bindings.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

PageContext
https://code.claude.com/docs/en/commandsPrimary /effort command entry still says no-argument usage only shows the current level
https://code.claude.com/docs/en/model-configDocuments /effort and effort sliders, but only explains slider navigation for /model
https://code.claude.com/docs/en/keybindingsCross-reference for the relevant selection/model-picker arrow-key and Enter bindings

Total scope: 3 pages affected

Source: Changelog v2.1.111

Exact changelog entry:

/effort now opens an interactive slider when called without arguments, with arrow-key navigation between levels and Enter to confirm

extent analysis

TL;DR

Update the documentation for the /effort command to reflect its new behavior of opening an interactive effort slider when invoked without an argument.

Guidance

  • Review the current documentation for /effort on the affected pages (commands reference, effort configuration, and model configuration) to identify outdated information.
  • Update the /effort entry in the commands reference to describe the new interactive slider behavior when called without an argument, using suggested wording: "Running /effort without an argument opens an interactive effort slider/picker. Use the arrow keys to move between effort levels and press Enter to confirm."
  • Consider adding a cross-reference to the relevant keyboard navigation page to clarify the standard select/model-picker bindings used by the interactive picker.
  • Verify that the updated documentation accurately reflects the current behavior of the /effort command, including the difference between invoking it with and without an argument.

Example

No code snippet is necessary for this issue, as it is related to documentation updates.

Notes

The suggested improvements should be applied to the three affected pages: commands reference, model configuration, and potentially the keyboard navigation page for cross-referencing.

Recommendation

Apply the workaround by updating the documentation to reflect the new behavior of the /effort command, as this will improve the accuracy and clarity of the documentation for users.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#ssr#memory leak#API versioning#request timeout

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix [DOCS] Commands reference shows outdated `/effort` no-argument behavior [1 participants]