2 people reported

All time, since Sep 21.

Ctrl+J newline can't be unbound

“Unbinding ctrl+j in ~/.claude/keybindings.json has no effect: pressing Ctrl+J in the chat input still inserts a newline.”

Is this your bug? What gets counted gets fixed. Pile on.

Paste this into your agent. It files your report, with your error and version.

I hit this bug: rapsheet.dev/sheets/claude-code/issues/3438/file
Follow it to file my report. Show me the text before you send.

No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends

Ctrl+J newline in chat input ignores keybinding unbind. Setting "ctrl+j": null in ~/.claude/keybindings.json has no effect, in the terminal chat input and the VS Code extension.

Is this your bug?

File my report
Where
chat input
Versions
2.1.278 to 2.1.301
Platforms
macOS, Windows
How bad
Breaks a normal workflow.

Part of: Prompt newline/send key bindings misbehave3 bugs

  1. Shift+Enter and Ctrl+Enter submit instead of newline on VTE/xterm3 people
  2. Ctrl+Enter doesn't send queued messages8 people

Original reports2, newest first

  1. VS Code extension: Ctrl+J newline is hardcoded in the chat input and can't be disabled#102749
  2. Ctrl+J / LF newline is hardcoded in the chat input, so unbinding ctrl+j in keybindings.json has no effect (breaks SKK IMEs)#95957

Do you work on Claude Code?

Claim its RAP Sheet to see what your users report and answer them in one place.