## Describe the bug Shift+Return (used for multi-line input) stopped working in v2.1.70. Pressing Shift+Return either sends the message or produces a backslash instead of inserting a newline. Works correctly on v2.1.69. ## To reproduce 1. Update Claude Code to v2.1.70 2. Start a conversation 3. Press Shift+Return to try to create a new line ## Expected behavior A newline is inserted in the input, allowing multi-line messages before sending. ## Confirmed regression - **v2.1.69**: Shift+Ret

Shift+Return no longer creates newline in input (regression in v2.1.70)

Status Fixed / completed

Maintainer reply None cached

Activity 5 comments · opened Mar 6, 2026 · closed Mar 6, 2026

Describe the bug

Shift+Return (used for multi-line input) stopped working in v2.1.70. Pressing Shift+Return either sends the message or produces a backslash instead of inserting a newline. Works correctly on v2.1.69.

To reproduce

Update Claude Code to v2.1.70
Start a conversation
Press Shift+Return to try to create a new line

Expected behavior

A newline is inserted in the input, allowing multi-line messages before sending.

Confirmed regression

v2.1.69: Shift+Return works correctly
v2.1.70: Shift+Return broken

Environment

Claude Code v2.1.70
macOS (Darwin 25.3.0)
Reproduces in both VS Code integrated terminal and Terminal.app

View original on GitHub ↗

5 Comments

github-actions[bot] · 5 months ago

Found 3 possible duplicate issues:

This issue will be automatically closed as a duplicate in 3 days.

If your issue is a duplicate, please close it and 👍 the existing issue instead
To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

naitokosuke · 5 months ago

For me(VS Code integrated teriminal user), this .vscode/settings.json ⬇️ works.

  // Former Config
  // {
  //     "key": "shift+enter",
  //     "command": "workbench.action.terminal.sendSequence",
  //     "args": {
  //         "text": "\\\r\n"
  //     },
  //     "when": "terminalFocus"
  // },
  {
      "key": "shift+enter",
      "command": "runCommands",
      "args": {
          "commands": [
              {
                  "command": "workbench.action.terminal.sendSequence",
                  "args": { "text": "\\" }
              },
              {
                  "command": "workbench.action.terminal.sendSequence",
                  "args": { "text": "\r" }
              }
          ]
      },
      "when": "terminalFocus"
  },

marciosete-cultureone · 5 months ago

naitokosuke solution worked for me too. vscode with claude code extension

naitokosuke · 5 months ago

Maybe this will fix 👀

https://github.com/anthropics/claude-code/issues/31347#issuecomment-4009477505

Resolved — root cause was a stale VS Code keybinding sending \\r\n instead of the correct escape sequence. Running /terminal-setup replaced it with the proper binding (\^[\r) and Shift+Enter works again.