[BUG] `/extra-usage` autocomplete collides with `/exit` — causes accidental admin requests

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

Related: #11928 (closed as not planned), but this is a higher-impact variant.

The CLI's autocomplete teaches users that /ex + Enter is the fastest way to exit a session. There's no reason to read the autocomplete dropdown — it works every time, so it becomes muscle memory.

Then, when a user approaches their usage limit, the autocomplete ranking changes. /ex + Enter no longer resolves to /exit — it resolves to /extra-usage, which sends a request to the org admin to approve additional spending. There's no confirmation step. By the time the user sees what happened, the request has already been sent. Muscle memory that was 100% safe yesterday now triggers a command that involves other people at your company, and the user only finds out after the fact.

This has caused multiple accidental admin requests on our team.

What Should Happen?

/ex + Enter should not change behavior based on hidden state. A command that sends requests to other people in your organization should not be one muscle-memory keystroke away from a common session command.

More generally, stateful commands (whose availability depends on session state like usage limits) should probably always autocomplete below non-stateful commands.

Or just always show all available commands, with some disabled, but still matching within the autocomplete.

Error Messages/Logs

N/A — no error is shown. The command executes successfully, which is the problem.

Steps to Reproduce

1. Use Claude Code regularly, building muscle memory that /ex + Enter exits the session 😇
2. Approach the usage limit
3. Type /ex + Enter as usual
4. Observe that an extra-usage request has been sent to your org admin instead of exiting

Claude Model

None

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.63 (Claude Code)

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

Workaround: Using /q instead of /exit avoids the issue, and org admins can disable the extra-usage request toggle (while keeping extra usage itself enabled). However, users won't know this is an issue until the first time it happens to them — so in practice, the workaround only helps after someone has already sent an unintentional request to their admin.