[DOCS] /extra-usage slash command is undocumented and incorrectly advertised to users

Resolved 💬 7 comments Opened Nov 25, 2025 by DavisWingard Closed Mar 8, 2026

Documentation Type

Missing documentation (feature not documented)

Documentation Location

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

Section/Topic

Incomplete Docs

Current Documentation

/extra-usage command is not documented.

What's Wrong or Missing?

Users are aggressively prompted to enable /extra-usage in order to "Access and configure extra usage to keep working when limits are hit" (terminal description). The command does not do either of these things in my experience, as running the command brings the user to a sign in window, and after they sign in, there is not a way to configure extra usage limits as is advertised in this page. Navigating to the usage settings does not offer a way to turn on/off or configure usage settings. Upon returning to the terminal, it appears that /extra-usage is now mysteriously enabled. Anthropic does state that "standard API rates apply", but it is unclear how to set a limit. Additionally, it does not appear that there is a CLI command that allows me to turn extra-usage off. I sincerely hope that this is a doc overlook and not a malicious attempt by anthropic to get users to "accidentally" spend credits that they don't realize they are using.

Suggested Improvement

  1. /extra-usage should be documented here: [https://code.claude.com/docs/en/slash-commands](url).
  2. Pro users should be able to configure rate limits for themselves when using extra-usage.
  3. The /extra-usage command should take users directly to the place that they can configure these limits.
  4. The /extra-usage command should be able to be turned off from the CLI.
  5. If requests 3 and 4 cannot be met, then I think a much more accurate description of the command would be "Turn on extra-usage".

Impact

High - Prevents users from using a feature

Additional Context

_No response_

View original on GitHub ↗

This issue has 7 comments on GitHub. Read the full discussion on GitHub ↗