Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [DOCS] Interactive mode and keybindings docs show outdated `Ctrl+L` behavior [1 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#49305•Fetched 2026-04-17 08:45:01
View on GitHub
Comments
0
Participants
1
Timeline
4
Reactions
0
Author
coygeekcoygeek
Participants
coygeekcoygeek
Timeline (top)
labeled ×4
RAW_BUFFERClick to expand / collapse

Documentation Type

Incorrect/outdated documentation

Documentation Location

https://code.claude.com/docs/en/interactive-mode

Section/Topic

Ctrl+L in the "Keyboard shortcuts" / "General controls" table, plus the default shortcut mappings on the keybindings page

Current Documentation

The docs currently say:

In Interactive mode → General controls: | Ctrl+L | Clear prompt input | Clears typed text, keeps conversation history |

In Customize keyboard shortcuts: | app:redraw | (unbound) | Force terminal redraw |

| chat:clearInput | Ctrl+L | Clear prompt input |

What's Wrong or Missing?

Changelog v2.1.111 says:

Ctrl+L now clears the screen and forces a full redraw — use this to recover when Cmd+K leaves the UI partially blank. Use Ctrl+U or double-Esc to clear prompt input.

The current docs still describe Ctrl+L as a prompt-clearing shortcut and show redraw as unbound.

A. Interactive mode documents the old behavior

Users reading the keyboard shortcut table are told that Ctrl+L clears typed text, but the release notes say the shortcut now exists to clear the screen and force a redraw.

B. Keybindings does not reflect the shipped default behavior

The keybindings reference still shows app:redraw as unbound and chat:clearInput on Ctrl+L, so it does not explain the current default shortcut behavior or point users to Ctrl+U / double-Esc for clearing prompt input.

Suggested Improvement

Update both pages to match the v2.1.111 behavior:

  • In Interactive mode, change the Ctrl+L row to describe clearing the screen and forcing a full redraw, including the recovery use case for partially blank UI.
  • In the same shortcut docs, point users to Ctrl+U or double-Esc for clearing prompt input.
  • In Customize keyboard shortcuts, clarify how the default Ctrl+L behavior relates to app:redraw and chat:clearInput so custom keybinding users know which action is actually bound by default.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

PageLine(s)Context
https://code.claude.com/docs/en/interactive-mode31Ctrl+L is documented as "Clear prompt input"
https://code.claude.com/docs/en/keybindings84, 105app:redraw is shown as unbound while chat:clearInput is bound to Ctrl+L

Total scope: 2 pages affected

Source: Changelog v2.1.111

Changelog entry:

Ctrl+L now clears the screen and forces a full redraw — use this to recover when Cmd+K leaves the UI partially blank. Use Ctrl+U or double-Esc to clear prompt input.

extent analysis

TL;DR

Update the documentation for Ctrl+L in the "Interactive mode" and "Customize keyboard shortcuts" pages to reflect the new behavior of clearing the screen and forcing a full redraw.

Guidance

  • Review the changelog entry for v2.1.111 to understand the intended behavior of Ctrl+L.
  • Update the "Interactive mode" documentation to describe Ctrl+L as clearing the screen and forcing a full redraw, including the recovery use case for partially blank UI.
  • Update the "Customize keyboard shortcuts" page to clarify the relationship between app:redraw and chat:clearInput and indicate that Ctrl+L is bound to the redraw action by default.
  • Verify that the updated documentation accurately reflects the current behavior of Ctrl+L and provides clear guidance for users.

Example

No code snippet is necessary for this issue, as it is a documentation update.

Notes

The issue is specific to the documentation and does not require any code changes. The updates should be made to the "Interactive mode" and "Customize keyboard shortcuts" pages, as specified in the issue.

Recommendation

Apply workaround: Update the documentation to reflect the correct behavior of Ctrl+L, as this will provide accurate guidance for users and resolve the issue.

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#ssr#conversation history#task chaining#parallel task

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING