Preflight Checklist
Problem Statement
In the Claude Code desktop app (Code tab), the Enter key always submits the chat message. There is no way to change this behavior.
The ~/.claude/keybindings.json feature (which supports remapping the submit key) only works in the CLI version and has no effect in the desktop app.
This makes it impossible to type multi-line messages naturally using Enter, and forces users to rely on workarounds.
Proposed Solution
Extend the ~/.claude/keybindings.json support to the Claude Code desktop app, so that users can remap the chat submit key (e.g. from Enter to Ctrl+Enter).
This would allow users to use Enter for newlines and Ctrl+Enter for submission, which is a common pattern in many chat and coding tools.
Alternative Solutions
Tried configuring ~/.claude/keybindings.json with "enter": null and "ctrl+enter": "chat:submit", but this has no effect in the desktop app — only works in the CLI version.
Priority
Medium - Would be very helpful
Feature Category
Configuration and settings
Use Case Example
No response
Additional Context
No response
Preflight Checklist
Problem Statement
In the Claude Code desktop app (Code tab), the Enter key always submits the chat message. There is no way to change this behavior.
The
~/.claude/keybindings.jsonfeature (which supports remapping the submit key) only works in the CLI version and has no effect in the desktop app.This makes it impossible to type multi-line messages naturally using Enter, and forces users to rely on workarounds.
Proposed Solution
Extend the
~/.claude/keybindings.jsonsupport to the Claude Code desktop app, so that users can remap the chat submit key (e.g. from Enter to Ctrl+Enter).This would allow users to use Enter for newlines and Ctrl+Enter for submission, which is a common pattern in many chat and coding tools.
Alternative Solutions
Tried configuring
~/.claude/keybindings.jsonwith"enter": nulland"ctrl+enter": "chat:submit", but this has no effect in the desktop app — only works in the CLI version.Priority
Medium - Would be very helpful
Feature Category
Configuration and settings
Use Case Example
No response
Additional Context
No response