codex - 💡(How to fix) Fix Add a setting for in-app browser annotation Enter behavior [4 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#23456Fetched 2026-05-20 03:49:46
View on GitHub
Comments
4
Participants
2
Timeline
8
Reactions
0
Author
Timeline (top)
commented ×4labeled ×3closed ×1

Error Message

A common workflow is to review a page, leave multiple precise annotations on different UI elements, and then send them as one batch to the agent. The new default makes this workflow more error-prone because a single Enter sends prematurely and exits the annotation collection flow.

Root Cause

A common workflow is to review a page, leave multiple precise annotations on different UI elements, and then send them as one batch to the agent. The new default makes this workflow more error-prone because a single Enter sends prematurely and exits the annotation collection flow.

At the same time, some users may prefer the new immediate-send behavior. That is exactly why this should be a user preference rather than a single fixed behavior.

RAW_BUFFERClick to expand / collapse

What is the feature request?

Please add a Codex app setting to customize the Enter-key behavior for in-app browser comments/annotations.

This follows #22719, where the immediate-send behavior was clarified as intentional. The request here is not only to revert the default, but to make the behavior configurable.

Current behavior

In the in-app browser annotation editor:

  • Enter sends the current browser comment immediately to the conversation.
  • Cmd+Enter commits/saves the current annotation and allows continuing to add more annotations before sending the final message.

For users whose main chat composer is configured to use Cmd+Enter to send, this creates an inverted shortcut model inside the same app:

  • Main chat composer: Cmd+Enter = send.
  • Browser annotation editor: Enter = send, Cmd+Enter = keep batching annotations.

That is hard to build muscle memory around.

Why this matters

A common workflow is to review a page, leave multiple precise annotations on different UI elements, and then send them as one batch to the agent. The new default makes this workflow more error-prone because a single Enter sends prematurely and exits the annotation collection flow.

At the same time, some users may prefer the new immediate-send behavior. That is exactly why this should be a user preference rather than a single fixed behavior.

Suggested setting

Add a setting such as:

In-app browser annotation Enter behavior

Options:

  1. Enter sends immediately
  2. Enter saves annotation / Cmd+Enter sends final message

Or phrase it around “single-comment mode” vs “batch annotation mode”.

The important part is that users who rely on multi-annotation batching can restore the previous workflow, while users who prefer immediate sending can keep the new default.

Environment

  • Codex desktop app on macOS
  • Observed after updating to 26.513.31313 / build 2867

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

codex - 💡(How to fix) Fix Add a setting for in-app browser annotation Enter behavior [4 comments, 2 participants]