[DOCS] Terminal config: Shift+Enter DOES work in JetBrains terminals when launched via the IDE plugin button

Status Open
Maintainer reply None cached
Activity 1 comment · opened Aug 11, 2026

Documentation Type

Incorrect/outdated documentation

Documentation Location

https://code.claude.com/docs/en/terminal-config

Section/Topic

Enter multiline prompts - terminal support matrix, JetBrains IDEs row

Current Documentation

The support matrix currently says:

| Terminal | Shift+Enter for newline |
|----------|------------------------|
| JetBrains IDEs such as PyCharm and Android Studio | Not available; use Ctrl+J or \ then Enter |

with no qualification about how the session was launched.

What's Wrong or Missing?

This is a documentation-only issue - no behavior change requested; the current behavior is better than documented.

Shift+Enter DOES insert a newline in IntelliJ IDEA's built-in terminal when Claude Code is launched from the JetBrains plugin's "Claude Code" button (with no pre-existing terminal session). Verified working on:

  • Windows 11 Home
  • IntelliJ IDEA with the Claude Code JetBrains plugin
  • Claude Code v2.1.228

Shift+Enter does NOT work when claude is started manually inside an already-open IntelliJ terminal session - presumably the case the matrix was written from. So the "Not available" claim is an overgeneralization: it depends on the launch path, most likely because the plugin only wires up Shift+Enter handling for terminal sessions it spawns itself.

Suggested Improvement

Split the JetBrains row (or add a footnote):

  • Sessions launched from the Claude Code plugin button: Shift+Enter works, no setup needed.
  • claude started manually in an existing JetBrains terminal: Shift+Enter not available; use Ctrl+J or \ then Enter (current guidance).

Also worth noting that relaunching via the plugin button is a fix if a user wants Shift+Enter.

Impact

Medium - Makes feature difficult to understand

Additional Context

_No response_

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗