[BUG] & [FEATURE] VSC | Accidental Approval on NUM key press during "Tell Claude what to do instead"

Resolved 💬 8 comments Opened Jan 13, 2026 by DrAlexHarrison Closed Mar 1, 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?

I just approved a major file edit from a plan document I was writing a detailed "Not yet, these corrections are needed" response to, in the Tell Claude what to do instead box below the multiple choice answers in the Accept this Plan? dialog.

I believe I hit the number 1 and Shift+Enter or Enter, or some other number key and then Shift+Enter or Enter.

Instead of sending my detailed comment to Claude, it selected Yes, and auto-accept.

What Should Happen?

When there are ≥1 character in the textbox in the Accept this plan? dialog:

  1. Enter safety: key press while dialog is active, it should submit the user's response only OR submit the user's response with No Keep Planning.
  2. Allow NUM keys: Number key presses should be entered into the textbox.
  3. Re-trigger safety delay: Departing from that textbox by any key press or mouse action (any user action ... or any action at all) should trigger the same safety delay that happens for any other action relating to that dialog as when the dialog first appears.

Error Messages/Logs

Just my panic-pressing `Esc` and clicking Stop frantically. :)

Steps to Reproduce

I don't really want to replicate it. ;)

I think:

  1. Build a plan doc with Claude in VS Code Editor.
  2. When prompted to approve, type in textbox, press a number key?
  3. Press enter?

Maybe an up arrow in there. I'm not sure.

Claude Model

Opus

Is this a regression?

No, this never worked

Last Working Version

_No response_

Claude Code Version

2.1.6

Platform

Other

Operating System

Ubuntu/Debian Linux

Terminal/Shell

VS Code integrated terminal

Additional Information

_No response_

View original on GitHub ↗

This issue has 8 comments on GitHub. Read the full discussion on GitHub ↗