claude-code - 💡(How to fix) Fix Permission prompt: inconsistent accept/reject key positions cause miskeys [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#46781Fetched 2026-04-12 13:33:11
View on GitHub
Comments
2
Participants
2
Timeline
2
Reactions
0
Author
Timeline (top)
commented ×2

Root Cause

The permission prompt key mappings are inconsistent — sometimes 2 means accept, other times 2 means reject. When you're in a flow approving/denying tool calls rapidly, it's very easy to accidentally approve or reject because the key positions swap meaning between prompts.

RAW_BUFFERClick to expand / collapse

Problem

The permission prompt key mappings are inconsistent — sometimes 2 means accept, other times 2 means reject. When you're in a flow approving/denying tool calls rapidly, it's very easy to accidentally approve or reject because the key positions swap meaning between prompts.

Expected Behavior

The reject/decline option should always be in a consistent, well-separated position from the accept keys. For example:

  • Accept: 1 or y
  • Reject: 5, 9, or n — something well away from accept so a miskey doesn't accidentally flip the intent

Impact

Users develop muscle memory for "1 = yes" but then get burned when a different prompt style maps 2 to something unexpected. This erodes trust in the permission system because you can't be sure what you just approved or denied.

Environment

  • Claude Code CLI on Windows 11
  • Heavy MCP tool usage (multiple tool calls per response)
  • Multiple permission prompts per session

extent analysis

TL;DR

Modify the permission prompt key mappings to ensure consistent and well-separated positions for accept and reject options.

Guidance

  • Review the Claude Code CLI documentation to understand how to customize permission prompt key mappings.
  • Identify the specific prompts where the key mappings are inconsistent and prioritize fixing those first.
  • Consider implementing a standardized key mapping scheme, such as using 1 or y for accept and 5, 9, or n for reject, to minimize errors.
  • Test the updated key mappings with heavy MCP tool usage to ensure the changes resolve the issue.

Example

No code snippet is provided as the issue does not imply a specific code change.

Notes

The solution may require updates to the Claude Code CLI configuration or code, depending on how the permission prompts are implemented.

Recommendation

Apply a workaround by standardizing the key mappings for permission prompts to ensure consistency, as upgrading to a fixed version is not mentioned in the issue. This approach allows for a quick resolution to the problem without waiting for a potential update.

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