[BUG] `Ctrl + e` or `⌘ + →` to explain permission requests breaks UX for "Tab to amend"

Resolved 💬 5 comments Opened Feb 8, 2026 by miteshashar Closed Apr 3, 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 the "Tab to amend" feature is available in permission requests along with Ctrl + e/⌘ + → to explain:

  • Claude code is overriding the default keybindings for navigating text in the terminal
  • This breaks the UX while drafting the amend message

What Should Happen?

While there are options to override keybindings, the default keybinding for the "explain" feature should ideally be different to not degrade the default UX.

Error Messages/Logs

Steps to Reproduce

  1. Ask Claude Code to run any bash command that would require a permission.
  2. Press Tab on either of the options to activate input for amend message.
  3. Type something
  4. Press Ctrl + a to go to beginning of the line.
  5. Press Ctrl + e/⌘ + → (intent: navigate cursor to the end of the line)

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.34

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Other

Additional Information

_No response_

View original on GitHub ↗

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