claude-code - 💡(How to fix) Fix Feature request: fixed numbers for permission prompts (0=No, 1=Yes, 2=Yes-all) [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

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#49643Fetched 2026-04-17 08:35:22
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Author
Timeline (top)
labeled ×3commented ×1

The permission prompt numbers are not consistent — the position/number for Yes/No/Yes-to-all varies by context, which makes it hard to build muscle memory.

Root Cause

The permission prompt numbers are not consistent — the position/number for Yes/No/Yes-to-all varies by context, which makes it hard to build muscle memory.

RAW_BUFFERClick to expand / collapse

Summary

The permission prompt numbers are not consistent — the position/number for Yes/No/Yes-to-all varies by context, which makes it hard to build muscle memory.

Suggestion

Use fixed, always-consistent numbers:

  • 0 — No
  • 1 — Yes
  • 2 — Yes to all future edits/reads

Why this helps

With fixed numbers, users can respond without reading the prompt each time. The current variable layout forces users to slow down and re-read the options on every prompt, which interrupts flow.

An alternative (or complement) would be single-key shortcuts: n, y, a.


Submitted on behalf of a user via Claude Code CLI.

extent analysis

TL;DR

Assigning fixed numbers to permission prompts, such as 0 for No, 1 for Yes, and 2 for Yes to all, can improve user experience by allowing for consistent and quicker responses.

Guidance

  • Consider implementing a standardized numbering system for permission prompts across all contexts to enhance user consistency and speed.
  • Evaluate the feasibility of introducing single-key shortcuts (e.g., n, y, a) as an alternative or complementary solution to fixed numbers.
  • Assess the impact of these changes on the overall user flow and muscle memory development.
  • Test the proposed solutions with a variety of users to validate the improvement in user experience.

Example

No specific code example is provided due to the nature of the issue focusing on user interface and experience rather than a specific coding problem.

Notes

The effectiveness of this solution may vary depending on the specific application, user base, and existing interface conventions. It's crucial to consider these factors during the implementation and testing phases.

Recommendation

Apply workaround: Implementing fixed numbers for permission prompts is a straightforward and potentially effective solution to improve user experience, assuming it aligns with the application's overall design and user interface guidelines.

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 Feature request: fixed numbers for permission prompts (0=No, 1=Yes, 2=Yes-all) [1 comments, 2 participants]