claude-code - 💡(How to fix) Fix Add confirmation prompt before sending `/extra-usage` request [2 comments, 2 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#47768Fetched 2026-04-15 06:42:54
View on GitHub
Comments
2
Participants
2
Timeline
4
Reactions
0
Timeline (top)
commented ×2labeled ×2

The /extra-usage command immediately sends a request to the organization admin without any confirmation prompt. This can lead to accidental requests being sent with no way to cancel them.

Root Cause

  • Accidental requests: Users may trigger the command unintentionally (e.g., exploring available commands, typos) and end up sending a request to their admin.
  • No undo: Once the request is sent, there is no built-in way to cancel it. The user must manually contact their admin to ask them to ignore it.
  • Consistency: Other potentially impactful CLI actions typically include a confirmation step before proceeding.

Fix Action

Fix / Workaround

Add a simple y/N confirmation prompt before the request is dispatched, defaulting to "No" to prevent accidental sends.

Code Example

This will send a request to your organization admin to enable extra usage. Proceed? [y/N]
RAW_BUFFERClick to expand / collapse

Description

The /extra-usage command immediately sends a request to the organization admin without any confirmation prompt. This can lead to accidental requests being sent with no way to cancel them.

Current Behavior

  1. User types /extra-usage
  2. Request is immediately sent to the admin
  3. Output: Request sent to your admin to enable extra usage.

There is no confirmation step and no way to cancel the request once sent.

Expected Behavior

A confirmation prompt should be shown before sending the request:

This will send a request to your organization admin to enable extra usage. Proceed? [y/N]

Only after the user confirms (e.g., typing y) should the request actually be sent.

Why This Matters

  • Accidental requests: Users may trigger the command unintentionally (e.g., exploring available commands, typos) and end up sending a request to their admin.
  • No undo: Once the request is sent, there is no built-in way to cancel it. The user must manually contact their admin to ask them to ignore it.
  • Consistency: Other potentially impactful CLI actions typically include a confirmation step before proceeding.

Suggested Solution

Add a simple y/N confirmation prompt before the request is dispatched, defaulting to "No" to prevent accidental sends.

extent analysis

TL;DR

Add a confirmation prompt before sending the /extra-usage request to prevent accidental sends.

Guidance

  • Modify the /extra-usage command to display a confirmation prompt, such as This will send a request to your organization admin to enable extra usage. Proceed? [y/N], before sending the request.
  • Set the default response to "No" to prevent accidental sends.
  • Only send the request if the user confirms by typing y.
  • Consider adding a cancel or undo mechanism for requests that have already been sent.

Example

def extra_usage_command():
    confirmation = input("This will send a request to your organization admin to enable extra usage. Proceed? [y/N] ")
    if confirmation.lower() == 'y':
        # Send the request to the admin
        print("Request sent to your admin to enable extra usage.")
    else:
        print("Request cancelled.")

Notes

This solution assumes that the /extra-usage command is implemented in a programming language that supports user input, such as Python. The exact implementation may vary depending on the language and framework used.

Recommendation

Apply the suggested solution by adding a confirmation prompt to the /extra-usage command, as it provides a simple and effective way to prevent accidental requests and improve the overall user experience.

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…

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 Add confirmation prompt before sending `/extra-usage` request [2 comments, 2 participants]