/usage-credits fires accidentally — autocomplete prefix-collision with /usage (relocated from the closed /extra-usage vs /exit issues)

Resolved 💬 0 comments Opened Jul 10, 2026 by nebasuke Closed Jul 14, 2026

Summary

Typing /usage (to open the read-only usage / rate-limit view) can accidentally
send a usage-credit-increase request to the org admin, because /usage and
/usage-credits share a prefix and sit adjacent in the slash-command autocomplete
menu. Pressing Enter/Tab accepts whichever entry is highlighted, so the
admin-facing command is one keystroke away from a routine read-only one.

This is the old collision, relocated by a rename

There is a prior cluster of issues, all closed as not planned, about the old
name /extra-usage colliding with /exit:

  • #36095 — /ext typo triggers /extra-usage instead of /exit
  • #37879 — /extra-usage autocomplete collides with /exit
  • #47768 — add a confirmation prompt before /extra-usage sends
  • #47111 — prompt before consuming extra usage credits on session limit

The command has since been renamed /extra-usage/usage-credits. That rename
did not fix the collision class — it moved it onto /usage, a command users
invoke deliberately and frequently to check their limits. So the near-miss is now
against a routine read-only command rather than /exit.

Steps to reproduce

  1. At the prompt, type /usage (intending to open the usage view).
  2. Press Enter (or Tab) without carefully checking which entry is highlighted.
  3. /usage-credits fires instead of /usage, sending a credit-limit-increase

request to the org admin.

Expected

Accepting /usage runs /usage. A command with an outward-facing, non-cancellable
side effect (notifying an admin) should not be one keystroke away from a read-only
command that shares its prefix.

Actual

/usage-credits is selected and immediately dispatches the admin request. There is
no confirmation step, and no way to cancel or recall it once sent — re-running just
reports You've already sent a usage credit request.

Impact

  • Silent, non-cancellable side effect (admin notification) triggered by a near-miss

on a common read-only command.

  • No local way to disable or hide the command — it is built-in (not in ~/.claude/,

and no config / keybinding / hook governs it).

Suggested fixes (any one helps)

  1. Add a confirmation prompt before /usage-credits sends (default No). This was

requested in #47768 and closed unaddressed.

  1. When the input exactly matches /usage, don't rank /usage-credits at/above

/usage in autocomplete.

  1. Provide a way to cancel/withdraw a pending credit request.
  2. Rename to remove the prefix collision entirely (e.g. /request-credits).

Environment

  • Claude Code 2.1.204
  • Linux (WSL2)

View original on GitHub ↗