[DOCS] Keybindings reference missing `chat:newline` action for configurable multi-line input
Documentation Type
Missing documentation (feature not documented)
Documentation Location
https://code.claude.com/docs/en/keybindings
https://code.claude.com/docs/en/terminal-config
Section/Topic
keybindingspage: Chat actions tableterminal-configpage: "Line breaks" guidance for custom keybindings
Current Documentation
keybindings currently lists these Chat actions:
chat:cancelchat:cycleModechat:modelPickerchat:thinkingTogglechat:submitchat:undochat:externalEditorchat:stashchat:imagePaste
No chat:newline action is documented.
terminal-config says:
"Keyboard shortcut: Set up a keybinding to insert a newline in other terminals"
But it does not specify which keybinding action performs newline insertion.
What's Wrong or Missing?
Claude Code v2.1.47 added a new keybinding action:
chat:newlinefor configurable multi-line input
That action is discoverable in release notes but not in documentation. Users who want Enter to insert newlines and another key to submit cannot discover the exact action name from docs.
Suggested Improvement
- Add
chat:newlineto the Chat actions table inkeybindings. - Include a short example config that maps Enter to newline and a different key to submit.
- Update
terminal-configline-break section to reference the exact action name (chat:newline) and cross-link tokeybindings.
Suggested example:
{
"bindings": [
{
"context": "Chat",
"bindings": {
"enter": "chat:newline",
"ctrl+j": "chat:submit"
}
}
]
}
Impact
Medium - Makes feature difficult to understand
Additional Context
Affected Pages:
| Page | Line(s) | Context |
|------|---------|---------|
| https://code.claude.com/docs/en/keybindings | 91-106 | Chat actions table omits chat:newline |
| https://code.claude.com/docs/en/terminal-config | 15-22 | Mentions "keyboard shortcut" for newline but not the action name |
Release note reference (v2.1.47):
- "Added
chat:newlinekeybinding action for configurable multi-line input"
Dedup check:
- Open issue #26477 requests adding the feature itself. This issue tracks post-release documentation coverage now that the feature exists.
This issue has 8 comments on GitHub. Read the full discussion on GitHub ↗