[BUG] When using `enter: chat:newline` in keybindings.json there are no other methods available to submit text messages
Status Fixed / completed
Reported on v2.1.133
Maintainer reply None cached
Activity 5 comments · opened May 8, 2026 · closed May 12, 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?
What's Wrong?
Adding enter: chat:newline to keybindings breaks all other chat:submit bindings for text messages.
What Should Happen?
What Should Happen?
meta+enter and cmd+enter should still submit text messages regardless of whether enter: chat:newline is present.
Environment
- macOS (Tahoe 26.4.1)
- Terminal: Warp v0.2026.04.29.08.57.stable_01
- Shell: zsh
- Claude Code: latest 2.1.133
Error Messages/Logs
Steps to Reproduce
Steps to Reproduce
Step 1 — Add these bindings and test:
{
"context": "Chat",
"bindings": {
"ctrl+enter": "chat:submit",
"meta+enter": "chat:submit",
"cmd+enter": "chat:submit"
}
}
Result: meta+enter and cmd+enter submit text correctly. ctrl+enter does not work.
Step 2 — Add enter: chat:newline and test again:
{
"context": "Chat",
"bindings": {
"enter": "chat:newline",
"ctrl+enter": "chat:submit",
"meta+enter": "chat:submit",
"cmd+enter": "chat:submit"
}
}
Result: ctrl+enter does nothing. meta+enter and cmd+enter now insert a newline instead of submitting. No binding submits a text message.
Claude Model
Sonnet (default)
Is this a regression?
I don't know
Last Working Version
_No response_
Claude Code Version
2.1.13
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
Warp
Additional Information
_No response_
5 Comments
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
My issue is slightly different to these other issues. For me,
"enter": "chat:newline"works, however it breaks the alternative methods to send text. Noting that it does still work for slash command submissions.I have the same issue as @Baanrow - searching for it brought me to this page, so I'm glad to at least know it's not just on my end.
@claude @sosukesuzuki @ByronAhn
The fix in v2.1.141 successfully resolved this for standard text prompts, however the bug is still present when using slash commands.
ctrl+enterdoes now correctly work for sending text prompts.enterdoes correctly create a new line in the input window.What's Wrong
ctrl+enterdoes not send the slash command.What Should Happen
ctrl+entershould send that slash command.This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.