[DOCS] Documentation Contradiction: Clarify `Shift+Enter` availability vs. `/terminal-setup` requirements

Documentation Type

Missing documentation (feature not documented)

Documentation Location

• https://code.claude.com/docs/en/terminal-config#line-breaks - https://code.claude.com/docs/en/interactive-mode#multiline-input

Section/Topic

• Multiline input and terminal configuration for line breaks.

Current Documentation

The Terminal Config page states:

"Run /terminal-setup within Claude Code to automatically configure Shift+Enter for VS Code, Alacritty, Zed, and Warp."

However, the Interactive Mode page and historical changelogs state:

"Shift+Enter works out of the box in iTerm2, WezTerm, Ghostty, and Kitty."

What's Wrong or Missing?

There is a logic contradiction that causes user confusion, particularly for VS Code users.

• One section implies Shift+Enter is a feature that might just work, while another implies a manual setup command is strictly required for specific environments like VS Code and Warp.
• The documentation does not sufficiently highlight the distinction between "native" terminal emulators (which support the sequence by default) and "integrated" or "GPU-accelerated" terminals that require the keybinding injection provided by /terminal-setup.

Suggested Improvement

Consolidate the information into a single, authoritative table or callout box in both locations to eliminate ambiguity.

Suggested Text:

### Entering Newlines Claude Code supports Shift+Enter for multiline input, but behavior varies by terminal: | Terminal Status | Terminal Apps | Action Required | | :--- | :--- | :--- | | Works Out of the Box | iTerm2, WezTerm, Ghostty, Kitty | None | | Requires Configuration | VS Code, Alacritty, Zed, Warp | Run /terminal-setup | Note: If you are using VS Code's integrated terminal, you must run /terminal-setup once to enable this behavior.

Impact

High - Prevents users from using a feature

Additional Context

• This issue is particularly relevant since version 2.1.0 changes.
• Links to related documentation:
• https://code.claude.com/docs/en/terminal-config
• https://code.claude.com/docs/en/interactive-mode