[DOCS] Fullscreen docs conflict on Escape interrupt vs clear-selection behavior

Open 💬 5 comments Opened Apr 4, 2026 by coygeek

Documentation Type

Incorrect/outdated documentation

Documentation Location

https://code.claude.com/docs/en/fullscreen

Section/Topic

Use the mouse / keyboard behavior when a fullscreen text selection is active while Claude is still processing

Current Documentation

The fullscreen page currently says:

Selected text copies to your clipboard automatically on mouse release. To turn this off, toggle Copy on select in /config. With it off, press Ctrl+Shift+c to copy manually. On terminals that support the kitty keyboard protocol, such as kitty, WezTerm, Ghostty, and iTerm2, Cmd+c also works. If you have a selection active, Ctrl+c copies instead of cancelling.

The terminal guide currently says:

* Press Esc to interrupt Claude if it's running.

The costs guide currently says:

* Course-correct early: If Claude starts heading the wrong direction, press Escape to stop immediately. Use /rewind or double-tap Escape to restore conversation and code to a previous checkpoint.

The keybindings reference currently says:

| app:interrupt | Ctrl+C | Cancel current operation | | footer:clearSelection | Escape | Clear footer selection |

What's Wrong or Missing?

Changelog v2.1.92 says:

Fixed misleading "esc to interrupt" hint appearing alongside "esc to clear" when a text selection exists in fullscreen mode during processing

Current docs still leave the Escape behavior inconsistent across pages:

A. Fullscreen selection behavior is incomplete

The fullscreen page explains how text selection and copy behave, but it does not explain what happens when a selection remains active while Claude is processing.

B. Other pages overstate Escape as an interrupt key

The terminal guide and costs guide tell users to press Escape to interrupt Claude, but the keybindings reference already shows that Ctrl+C is the app-level interrupt and Escape is also used to clear footer selection.

That means the docs do not clearly explain the fullscreen case that v2.1.92 had to fix: Esc can be associated with clearing an active selection rather than interrupting the running turn.

Suggested Improvement

Add a short note to the fullscreen page near the text-selection paragraph that explains the active-selection case explicitly, for example:

When a text selection is active in fullscreen, Esc clears the selection. Use Ctrl+C to interrupt a running turn.

Then reconcile other user-facing shortcut guidance so it does not present Escape as a universal interrupt key. In particular:

  • update terminal-guide and costs to recommend Ctrl+C as the reliable interrupt shortcut
  • cross-reference interactive-mode or keybindings for the canonical shortcut table

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

| Page | Context |
|------|---------|
| https://code.claude.com/docs/en/fullscreen | Fullscreen text selection and copy behavior; missing active-selection Escape guidance |
| https://code.claude.com/docs/en/terminal-guide | Beginner guidance currently says Esc interrupts Claude |
| https://code.claude.com/docs/en/costs | Cost-control guidance currently says to press Escape to stop immediately |
| https://code.claude.com/docs/en/interactive-mode | Canonical shortcut reference already lists Ctrl+C as the standard interrupt |
| https://code.claude.com/docs/en/keybindings | Documents app:interrupt as Ctrl+C and footer:clearSelection as Escape |

Total scope: 5 pages affected

Source: Changelog v2.1.92

Exact changelog entry: Fixed misleading "esc to interrupt" hint appearing alongside "esc to clear" when a text selection exists in fullscreen mode during processing

View original on GitHub ↗

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