[FEATURE] No way to insert a newline in the agent view dispatch input (Shift+Enter dispatches)

Summary

There is no way to insert a literal newline in the agent view dispatch input. In the agent view, both Enter and Shift+Enter are bound to dispatch actions, so neither can be used to compose a multi-line task description inline the way Shift+Enter works in the normal chat prompt.

This is a follow-up to #60396 (auto-closed as NOT_PLANNED by the stale bot for inactivity, not actually resolved — two users confirmed the gap there).

Environment

• Version: 2.1.209 (Claude Code)
• Platform: darwin (macOS)
• Terminal: xterm-256color

Note: Shift+Enter inserts newlines correctly in the main chat prompt in this same terminal, so this is not a terminal-config / /terminal-setup issue — it is specific to the agent view's keybinding context.

Current documented agent-view dispatch keybindings

Per https://code.claude.com/docs/en/agent-view.md:

| Key | Action |
|---|---|
| Enter | Dispatch the task (or attach to selected session) |
| Shift+Enter | Dispatch and immediately attach to the new session |
| Ctrl+G | Open the dispatch prompt in $VISUAL / $EDITOR |

There is no documented key that inserts a newline into the dispatch input itself.

Steps to reproduce

1. Open the agent view.
2. Focus the task-description / dispatch input.
3. Type some text, then try to start a second line with Enter or Shift+Enter.
4. Instead of a newline, the task is dispatched (Shift+Enter dispatches and attaches).

Expected

A key should insert a literal newline in the dispatch input without dispatching, so multi-line task descriptions can be composed inline — matching the affordance the main chat prompt already provides.

Suggested fix

Bind a plain newline key in the dispatch input context. Ctrl+J is already bound to chat:newline in the chat context and would be a natural, consistent choice here. Ctrl+G (open external editor) is a workaround but requires leaving the input for a full editor round-trip just to add a line break.

Alternatively, if a binding already exists but is intentionally undocumented, documenting it in the agent-view keybindings reference would resolve this.

Related

• #60396 — "[Bug] Ctrl+Shift+Enter not triggering newline in Claude agent view" (closed as NOT_PLANNED by inactivity bot; prior art with a second confirming user)