Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix UI bug: Permission prompt button order (Yes/No) is inconsistent across prompts [1 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#55603•Fetched 2026-05-03 04:49:10
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Author
ysielabsysielabs
Participants
github-actions[bot]github-actions[bot]ysielabsysielabs
Timeline (top)
labeled ×3commented ×1

Error Message

Error Messages/Logs

Root Cause

Please correct and standardize by simply swapping "1 and 2 between Yes/No depending on context. So the fixed should be: "1 [ALWAYS] =No; 2 [ALWAYS] =Yes; 3 [ALWAYS]=Yes+don't ask again" and then track the reduction of user errors who formerly, regrettably hit "2" and then had to stop and take the added time to correct it, because they thought they hit "Yes, don't ask again" but that option had been removed.

RAW_BUFFERClick to expand / collapse

Preflight Checklist

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

What's Wrong?

Permission prompt button order is inconsistent and thus inefficient and illogical, especially when there is an easy fix. That is, where now sometimes 1=Yes/2=No, and sometimes its reversed.

What Should Happen?

Please correct and standardize by simply swapping "1 and 2 between Yes/No depending on context. So the fixed should be: "1 [ALWAYS] =No; 2 [ALWAYS] =Yes; 3 [ALWAYS]=Yes+don't ask again" and then track the reduction of user errors who formerly, regrettably hit "2" and then had to stop and take the added time to correct it, because they thought they hit "Yes, don't ask again" but that option had been removed.

Error Messages/Logs

Steps to Reproduce

Since Claude asks you yes/no questions repeatedly - just track your historical data regarding the number of times people had to go back correct the input.

Claude Model

Sonnet (default)

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

Claude Sonnet 4.6

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Terminal.app (macOS)

Additional Information

No response

extent analysis

TL;DR

Standardize the permission prompt button order by swapping "1" and "2" to consistently map "1" to "No" and "2" to "Yes".

Guidance

  • Review the current implementation of the permission prompt to identify where the inconsistent button order is introduced.
  • Update the code to standardize the button order, ensuring "1" always corresponds to "No" and "2" to "Yes", with "3" being "Yes, don't ask again".
  • Track user interactions to monitor the reduction in errors after implementing the fix.
  • Consider adding automated tests to verify the consistency of the button order across different scenarios.

Notes

The provided information does not include specific code snippets or technical details, so the guidance is based on the described behavior and expected fix.

Recommendation

Apply workaround: Standardize the button order as described to improve user experience and reduce errors, as the issue is reported as a regression and the exact cause or previous working version is not specified.

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#LLM response#prompt template#agent execution#callback error

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 UI bug: Permission prompt button order (Yes/No) is inconsistent across prompts [1 comments, 2 participants]