### 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 - `keybindings` page: Chat actions table - `terminal-config` page: "Line breaks" guidance for custom keybindings ### Current Documentation `keybindings` currently lists these Chat actions: - `chat:cancel` - `chat:cycleMode` - `chat:modelPicker` - `chat:thinkingToggle` - `chat:submi

[DOCS] Keybindings reference missing `chat:newline` action for configurable multi-line input

Status Fixed / completed

Maintainer reply None cached

Workaround ✓ Mentioned in thread ↓

Activity 8 comments · opened Feb 18, 2026 · closed Apr 28, 2026

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

keybindings page: Chat actions table
terminal-config page: "Line breaks" guidance for custom keybindings

Current Documentation

keybindings currently lists these Chat actions:

chat:cancel
chat:cycleMode
chat:modelPicker
chat:thinkingToggle
chat:submit
chat:undo
chat:externalEditor
chat:stash
chat: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:newline for 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:newline to the Chat actions table in keybindings.
Include a short example config that maps Enter to newline and a different key to submit.
Update terminal-config line-break section to reference the exact action name (chat:newline) and cross-link to keybindings.

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:newline keybinding 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.

View original on GitHub ↗

8 Comments

github-actions[bot] · 6 months ago

Found 3 possible duplicate issues:

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

guppy-jpf · 6 months ago

in addition, the keybindings doc page states:

Run /keybindings to create or open your configuration file

when i just tried that in CC 2.1.47, it didn't show up in the slash-command autocomplete, and when i tried it anyway, it said:

Unknown skill: keybindings

while i appreciate that this appears to now be finally customizable, documentation needs to be consistently updated when features are added, so that the release notes don't end up being an empty gift box half the time ...

update: moreover, i can't even get the feature to work, no matter what i put in keybindings.json. as expected, CC itself is no help, displaying its usual lack of self-awareness

GregEisenberg · 6 months ago

I was just about to submit the same complaint

Feature Request: Default keybinding for newline in chat input

Summary

There is no default keybinding to insert a newline in the chat input. This makes composing multi-line prompts unnecessarily difficult, and multi-line prompts are important for writing clear, structured instructions.

Current behavior

enter submits the message (the only default chat input binding)
chat:newline has no default keybinding
The natural choice shift+enter does not work because most terminal emulators send the same keycode for shift+enter and enter — they are indistinguishable

Workarounds that exist today

ctrl+g to open an external editor — works, but can conflict with other apps (e.g., Gemini uses ctrl+g globally on macOS)
Backslash \ continuation before pressing enter — works, but not intuitive
Pasting multi-line text from clipboard — works, but breaks the flow

Suggestion

Assign a default keybinding to chat:newline that actually works in terminals. alt+enter (or option+enter on macOS) is distinguishable from enter in most terminal emulators and is a common newline convention in other tools (Slack, JetBrains IDEs, etc.).

Why this matters

Good prompts are often multi-line — numbered instructions, code blocks, structured context. Making newline entry frictionless would improve the experience for everyone using Claude Code in the terminal.

Environment

macOS (Terminal / iTerm2)
Claude Code CLI

coygeek · 5 months ago

Still unresolved as of 2026-03-17. chat:newline does not appear in the keybindings reference page despite being confirmed in the changelog.

coygeek · 5 months ago

Correction after a full re-verification on 2026-04-01: this issue is still only partially resolved, not resolved. The keybindings page now documents chat:newline, but the terminal-config page still tells users to set up a newline shortcut without naming or linking to the chat:newline action, so this should remain open.

raffishquartan · 5 months ago

Setting chat:newline did not work for me

coygeek · 4 months ago

Issue #26708 Verification

Title: [DOCS] Keybindings reference missing chat:newline action for configurable multi-line input
Issue Date: (filed pre-verification)
Verification Date: 2026-04-27
Status: RESOLVED

Issue Summary

The issue reported that the chat:newline keybinding action (added in v2.1.47 / changelog entry referencing PR #26075) was missing from the keybindings documentation page and that the terminal-config page referenced a "keyboard shortcut" for newline insertion without naming the specific action. Three documentation gaps were identified:

chat:newline absent from the Chat actions table on the keybindings page
No example config showing Enter mapped to newline with an alternate submit key
terminal-config page did not reference the chat:newline action name or cross-link to keybindings

Verification Results

Claim 1: `chat:newline` missing from Chat actions table on keybindings page

Status: RESOLVED
Evidence: The keybindings page (/docs/en/keybindings) now lists chat:newline at line 112 in the Chat actions table:

> | chat:newline | Ctrl+J | Insert a newline without submitting |

Verdict: The action is fully documented with action name, default binding, and description.

Claim 2: No example config showing Enter-to-newline with alternate submit key

Status: RESOLVED
Evidence: The keybindings page includes an example at lines 403-416 that maps ctrl+x to chat:newline in the Chat context, demonstrating the chord-unbinding pattern needed to remap newline. The terminal-config page at line 36 explicitly instructs:

> "To bind newline to a different key, or to swap behavior so Enter inserts a newline and Shift+Enter submits, map the chat:newline and chat:submit actions in your keybindings file."

Verdict: Both a code example and prose guidance are present.

Claim 3: `terminal-config` page does not reference `chat:newline` action name or cross-link

Status: RESOLVED
Evidence: The terminal-config page at line 36 names both chat:newline and chat:submit action names and links to the keybindings page ([keybindings file](https://code.claude.com/docs/en/keybindings)). Line 18 also provides a general cross-link: "To change which keys Claude Code itself responds to, see keybindings instead."
Verdict: The action name and cross-link are both present.

Current State

| Location | Before | After |
|----------|--------|-------|
| keybindings.md Chat actions table (line 112) | chat:newline missing | chat:newline documented with default Ctrl+J and description |
| keybindings.md example config (lines 403-416) | No newline remapping example | Example showing ctrl+x mapped to chat:newline |
| terminal-config.md line 36 | Vague "keyboard shortcut" reference | Explicit chat:newline and chat:submit action names with cross-link |

Suggested Fix

N/A — all requested documentation changes have been applied.

References

Keybindings page: https://code.claude.com/docs/en/keybindings
Terminal config page: https://code.claude.com/docs/en/terminal-config
Changelog entry for the feature: changelog.md line 1589 ("Added chat:newline keybinding action for configurable multi-line input")

Conclusion & Recommendation

Primary Concern: The chat:newline keybinding action was not documented after being added in a release.
Resolution Status: Fully resolved. All three documentation gaps identified in the issue have been addressed in the current docs mirror.
Recommendation: Close as completed.

github-actions[bot] · 2 months ago

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.