Desktop app: option to make Enter queue an inline annotation instead of sending immediately

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

Feature description

In the Claude Code desktop app, when you highlight a piece of the transcript and type an inline annotation/comment, pressing Enter sends the message and starts Claude working immediately.

I'd like the option to swap this around, matching how other tools (e.g. ChatGPT Codex) handle selection annotations:

• Enter on an annotation -> add it to the composer/prompt as a pending annotation (do not send). This lets me highlight several passages, comment on each, and build up one combined message.
• Ctrl+Enter -> send immediately (today's Enter behaviour).

Today there is no way to batch multiple annotations from an idle session - each Enter fires a separate turn. The keybindings system (~/.claude/keybindings.json) exposes chat:submit / chat:queueSubmit for the main composer, but there is no context or action for the inline annotation widget, so this cannot be remapped by users.

Suggested fix

Either:

1. Add an annotation context + actions to the keybindings system so Enter/Ctrl+Enter can be remapped, or
2. Add a setting: "Enter queues annotation, Ctrl+Enter sends" (defaulting to current behaviour).

Environment

• Claude Code desktop app, Windows 11

Proposed Solution

In the annotation comment box:

• Enter adds the annotation + comment to the main composer as a pending item (nothing is sent). I can then highlight more text and add further annotations the same way.
• Ctrl+Enter (or Enter in the main composer) sends everything as one message and starts the turn.

Alternatively, expose the annotation widget as a context in ~/.claude/keybindings.json with submit/queue actions so users can remap Enter and Ctrl+Enter themselves.

Alternative Solutions

Checked ~/.claude/keybindings.json - the annotation widget has no context or action, so it cannot be remapped. The main composer's chat:queueSubmit only applies to the chat input, not annotations. There is no workaround from an idle session: each annotation Enter starts a separate turn.

Priority

Critical - Blocking my work

Feature Category

CLI commands and flags

Use Case Example

Example: reviewing a long plan Claude produced, I want to highlight five different lines and leave a comment on each (agree / change this / drop this). Today the first Enter starts Claude working on comment 1 alone; the other four have to wait or interrupt. With this feature I would queue all five and send once.

Additional Context

_No response_