claude-code - 💡(How to fix) Fix [FEATURE] Add chat:deleteToLineStart action (Ctrl+U clears all input instead of kill-to-beginning-of-line) [1 comments, 2 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#51694Fetched 2026-04-22 07:55:22
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Author
Participants
Timeline (top)
labeled ×3commented ×1
RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing requests and this feature hasn't been requested yet
  • This is a single feature request (not multiple features)

Problem Statement

Problem

Ctrl+U in the chat input clears all content instead of performing the standard readline kill-to-beginning-of-line behavior. There is no chat:deleteToLineStart action available in keybindings.json to customize this.

Impact

Users with iTerm2 configured to send 0x15 (Ctrl+U) on Cmd+Backspace lose the ability to delete the current line. Option+Delete (delete word) works, but there's no way to delete an entire line without clearing all input.

Proposed Solution

Add a chat:deleteToLineStart action that can be bound via keybindings.json, and ideally make Ctrl+U default to this rather than chat:clearInput.

Alternative Solutions

No response

Priority

Critical - Blocking my work

Feature Category

Interactive mode (TUI)

Use Case Example

No response

Additional Context

No response

extent analysis

TL;DR

Adding a chat:deleteToLineStart action to keybindings.json and binding it to Ctrl+U may resolve the issue.

Guidance

  • Investigate the current keybindings in keybindings.json to understand how Ctrl+U is currently mapped and if there's a way to override its behavior without adding a new action.
  • Consider reaching out to the developers or checking the documentation to see if there's an existing action that can be used to achieve the kill-to-beginning-of-line behavior.
  • If adding a new action is necessary, propose a patch or pull request to include chat:deleteToLineStart in the codebase.
  • Test any changes or workarounds in a controlled environment to ensure they don't introduce new issues.

Example

No code example is provided as the issue does not include specific code snippets or APIs to work with.

Notes

The solution relies on the assumption that adding a new action to keybindings.json is feasible and will be accepted by the maintainers. There might be technical limitations or design decisions that prevent this approach.

Recommendation

Apply workaround: Until the chat:deleteToLineStart action is officially added, users can try to find an alternative keybinding or submit a patch to include this feature, as the current behavior is blocking critical work.

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…

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 [FEATURE] Add chat:deleteToLineStart action (Ctrl+U clears all input instead of kill-to-beginning-of-line) [1 comments, 2 participants]