Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] v2.1.111: Ctrl+W and Ctrl+U default bindings changed, shadowing readline delete-word and delete-to-line-start [2 comments, 3 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#49317•Fetched 2026-04-17 08:44:40
View on GitHub
Comments
2
Participants
3
Timeline
10
Reactions
4
Author
KosmoCHEKosmoCHE
Participants
kennfatkennfatKosmoCHEKosmoCHEshinya2020shinya2020
Timeline (top)
labeled ×5commented ×2cross-referenced ×2subscribed ×1

Error Message

Error Messages/Logs

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?

After updating to v2.1.111 on macOS (iTerm2/Terminal.app), Ctrl+W now deletes to start of line instead of deleting the previous word, and Ctrl+U behavior also changed. Worked correctly on v2.1.110.

  • Ctrl+W: delete to start of line
  • Ctrl+U: delete entire input

What Should Happen?

  • Ctrl+W: delete previous word (werase)
  • Ctrl+U: delete to start of line (kill line backward)

Error Messages/Logs

Steps to Reproduce

  1. Update to v2.1.111 (macOS, iTerm2/Terminal)
  2. claude → type hello world foo bar → press Ctrl+W

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

2.1.99

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

iTerm2

Additional Information

No response

extent analysis

TL;DR

Downgrade to version 2.1.110 to potentially resolve the issue with Ctrl+W and Ctrl+U keyboard shortcuts.

Guidance

  • Verify that the issue is specific to version 2.1.111 by testing the same shortcuts in version 2.1.110.
  • Check if the problem persists across different terminals (e.g., Terminal.app) to isolate if it's a terminal-specific issue or a Claude Code issue.
  • Test other keyboard shortcuts to see if the problem is limited to Ctrl+W and Ctrl+U or if there are broader issues with keyboard input handling.

Example

No specific code example is applicable in this case, as the issue seems related to version-specific behavior rather than code implementation.

Notes

The fix is based on the information that the issue arose after updating to version 2.1.111 and that it worked correctly in version 2.1.110. This suggests a regression introduced in the update.

Recommendation

Apply workaround: Downgrade to version 2.1.110, as it is confirmed to work correctly with the expected behavior of Ctrl+W and Ctrl+U shortcuts.

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#batch processing#GPU compatibility#latency issue#model 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