[BUG] Shift+Enter in Claude for Windows No Longer Works for NewLine

Status Open
Maintainer reply None cached
Activity 10 comments · opened Feb 11, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

In previous versions of Claude Code for Windows (probably 2 or 3 versions ago now) I was able to hit Shift+Enter, and get to a new line to continue adding info. Now when i hit it, it just sends the message right away. There's no longer a way to get to new line.

I've tried Shift+Enter, CTRL+Enter, and Alt+Enter and none of them work.

What Should Happen?

Shift+Enter should've gone to the next line instead of sending my reply.

Error Messages/Logs

Steps to Reproduce

  1. Open a new chat.
  2. Write some text.
  3. Click Shift+Enter

Claude Model

Not sure / Multiple models

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

1.1.2685 (f39a62)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Other

Additional Information

using Claude for Windows.

View original on GitHub ↗

8 Comments

github-actions[bot] · 6 months ago

Found 3 possible duplicate issues:

  1. https://github.com/anthropics/claude-code/issues/25054
  2. https://github.com/anthropics/claude-code/issues/22719
  3. https://github.com/anthropics/claude-code/issues/1262

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

OnlyTakesAshot · 6 months ago

This is a new issue that isn't covered by those. The other open bugs are for MacOS or for other ways of accessing Claude Code.

AfterRealm · 6 months ago

Mine was fine the last few days! Then all of a sudden today, it stopped working in my Code Desktop for Windows. There wasn't even an update, I had installed the update this morning!

jhardin-accumula · 6 months ago

2026-02-24 Still occurring in Claude Code 2.1.52 on Windows. [CTRL]+[ENTER] does work (for me).

jhardin-accumula · 6 months ago

2026-03-02 Still occurring in Claude Code 2.1.63 on Windows. [CTRL]+[ENTER] does work (for me).

jhardin-accumula · 5 months ago

2026-03-04 Still occurring in Claude Code 2.1.68 on Windows. [CTRL]+[ENTER] does work (for me).

Budgulick · 5 months ago

Workaround: Shift+Enter for newline in Claude Code on Windows Terminal

Verified working on:

  • Windows 11 Pro (10.0.26200)
  • Windows Terminal 1.23.20211.0
  • Claude Code 2.1.70

The root cause is that Windows Terminal sends the same byte (CR) for both Enter and Shift+Enter — the terminal can't distinguish them. The fix requires two changes:

1. Windows Terminal — teach it to send a distinct escape sequence for Shift+Enter

In %LOCALAPPDATA%\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\LocalState\settings.json, add to actions:

{
    "command": {
        "action": "sendInput",
        "input": "\^[[13;2u"
    },
    "id": "User.sendInput.ShiftEnter"
}

And add to keybindings:

{
    "id": "User.sendInput.ShiftEnter",
    "keys": "shift+enter"
}

2. Claude Code — map Shift+Enter to newline

In ~/.claude/keybindings.json:

{
  "$schema": "https://www.schemastore.org/claude-code-keybindings.json",
  "$docs": "https://code.claude.com/docs/en/keybindings",
  "bindings": [
    {
      "context": "Chat",
      "bindings": {
        "shift+enter": "chat:newline"
      }
    }
  ]
}

Restart Windows Terminal after both changes. Shift+Enter will insert a newline, Enter will send — matching Claude.ai and Claude Desktop behavior.

skidrow88 · 5 months ago

On MacOS

/terminal-setup                                                                                                                                                                   
  ⎿  Installed VSCode terminal Shift+Enter key binding

Showing cached comments. Read the full discussion on GitHub ↗