[BUG] Option 3 'tell Claude what to do differently' input is clobbered by incoming permission requests

Resolved 💬 1 comment Opened May 19, 2026 by cdSheriff Closed Jun 18, 2026

Preflight Checklist

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

What's Wrong?

When Claude Code asks permission to perform a task (use gh api, search the web, fetch something) and I select Option 3: No, and tell claude what to do differently I can't ever tell Claude what to do differently because the UX gets bogged down with successive requests for permission. The successive tool use requests block the input window. The only options are to silently deny and hope it doesn't matter, or esc out and interrupt ALL activity to change the action for one single path

What Should Happen?

select Option 3: No, and tell claude what to do differently and see the text input, which holds as long as the user is typing feedback, with a timeout to silently drop the tool use prompt and continue. Other tool requests queue until user finishes input or timeout

Error Messages/Logs

Steps to Reproduce

  1. Tell claude to do something
  2. see claude ask permission to bash rm -rf
  3. deny permission, decide to type a different command to use
  4. slowly drown in a flood of interruptions from permission requests that block all typing

Claude Model

Sonnet (default)

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

v2.1.144

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗