Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] Consecutive permission prompts replace each other with no input cooldown — user approves an unread prompt (safety regression)

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…

Error Message

Error Messages/Logs

Root Cause

What happens: When two permission prompts fire in close succession, prompt B replaces prompt A in place. If the user has read prompt A and is moving to approve it, their confirmation keystroke lands on prompt B, which was never seen. I have approved actions I did not read multiple times this morning because of this. It may be during firing off multiple subagents at the same time.

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?

What happens: When two permission prompts fire in close succession, prompt B replaces prompt A in place. If the user has read prompt A and is moving to approve it, their confirmation keystroke lands on prompt B, which was never seen. I have approved actions I did not read multiple times this morning because of this. It may be during firing off multiple subagents at the same time.

Why this is a safety bug, not UX: The entire point of the permission gate is informed consent. Replacing the prompt content under a primed keystroke, with no re-arm delay, defeats it. The user authorizes an action they never reviewed. This is worse than #48550 because it bypasses review entirely rather than just changing a default.

Environment:

  • Claude Code 2.1.143 (latest)
  • Linux
  • Regression, did not occur before this week. The permission/input-handling area changed in 2.1.139–2.1.141 ("Numerous input handling and permission-related fixes"), the likely regression window.

What Should Happen?

Permission prompts queue like they used to, they don't show on top of the current prompt.

Error Messages/Logs

Steps to Reproduce

  1. Ask Claude Code to do work (maybe: using subagents)
  2. Prompts coming in show on top of the other prompts.

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

unsure, before maybe Wednesday of this week it was working

Claude Code Version

2.1.143

Platform

Anthropic API

Operating System

Ubuntu/Debian Linux

Terminal/Shell

Other

Additional Information

In tmux in konsole

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#environment variable#network issue#logging issue#authentication issue

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 [BUG] Consecutive permission prompts replace each other with no input cooldown — user approves an unread prompt (safety regression)