In-app browser comments submit immediately on Enter instead of allowing multiple annotations
What happened?
After a recent Codex app update, the in-app browser comment/annotation flow appears to have regressed. Previously, I could add multiple comments/annotations in the in-app browser before submitting them as one message. Now, after typing a comment and pressing Enter, the comment is immediately sent to the conversation/chat, so I cannot add more than one annotation before dispatch.
Steps to reproduce
- Open the Codex desktop app.
- Open the in-app browser.
- Start leaving a browser comment/annotation on the page.
- Type comment text.
- Press Enter.
- Try to add another browser comment before sending the overall prompt.
Expected behavior
Pressing Enter in the browser comment editor should commit/save that annotation locally and keep the user in the annotation flow so multiple comments can be collected, or otherwise preserve the previous multi-comment workflow.
Actual behavior
The first comment is immediately sent to the conversation/chat as a message/turn. This exits the annotation collection flow and prevents adding multiple comments before sending.
Regression
This started after a recent app update. The previous behavior allowed multiple in-app browser annotations before sending.
Notes from code inspection
I pulled origin/main to 7c11c14efc693c19f59dadfccc7abcdc35bbaf89. The open-source repo does not appear to contain the desktop in-app browser comments UI itself. The app-server side treats turn/start as a send/generate operation (TurnStartParams.input -> Op::UserInput), so if the client now routes each browser comment through turn/start on Enter, the observed immediate-send behavior would be expected from the server side. This may be a desktop client/UI regression rather than an app-server regression.
12 Comments
⌘Enter can solve this problem
Thanks,
⌘Entersolves this for me. Appreciate the quick tip.It is a little less convenient than the previous behavior, but this is enough to unblock me.
This is by design, we changed the default behavior to send individual comments immediately on Enter so the default behavior is simpler for most people to understand.
This regression irritates me terribly.
I normally send multiple annotations per each page and ask agent to process them as a batch.
How to change that behavior back? I want to use Enter to send a single comment.
hard to believe this was a ux decision...
No way this was done for ux reasons guys, give us a choice in settings to make the behaviour we like
That is so dumb. Please change that.
I absolutely hate the single annotation sending by Enter. I used to ask for ~10-20 annotations before sending it. Right now I have to remember to hold Ctrl. I do not want it and I hate that I can't change it. Terrible UX change.
@bschoepke-openai Thanks for clarifying that the new immediate-send behavior is by design.
Could the in-app browser annotation Enter behavior be made configurable, or follow the existing main composer send-shortcut preference?
The main chat composer already lets users customize the send shortcut. In my setup, the composer is configured so
Cmd+Entersends. The confusing part is that browser annotations now use the opposite mental model:Entersends immediately, whileCmd+Enterkeeps batching annotations.For users who review a page by placing multiple annotations on different UI elements before sending one final instruction to the agent, the previous batching workflow is important. At the same time, I understand some users may prefer the new immediate-send default. A setting would let both workflows coexist without forcing one shortcut model on everyone.
A setting like “In-app browser annotation Enter behavior” with options such as “Enter sends immediately” and “Enter saves annotation / keep batching” would solve this cleanly.
Adding one Windows-specific data point from #23871 before closing that issue as a duplicate:
Ctrl+Enterqueues/adds the current in-app browser annotation and preserves the multi-annotation workflow.Enter/ clicking the arrow sends immediately.It would still help to either document the shortcut clearly, show it in the annotation submit tooltip, or expose a setting for the default annotation behavior.
Environment observed: Codex Desktop on Windows, app version
26.513.4821.0.this is stupid, it was not confusing and i have been pulling my hair out as to why it stopped working why i could not annotate many times then go into the chat to submit.
stop forcing ux on people,, if you want to do such a thing, then make a setting for it and let the user decide, i have wasted so much time of the last weeks waiting on it to finish 1 annotation at a time since i thought this was a bug, yet you genius thought this was a good idea to change how it works, thanks so much...
who ever is in control of ui ux should be fired for allowing this , im so sick of companies who are clueless. this is microscopic level stupid.
i have wasted so much time and frustration over this thinking yall we not aware of a bug, only to find out this was your intended method that a secret hotkey is now what i should be using ..
even worse now i get this stupid blue bar about annotations i need to click the x on the far left side as you have removed the blue bar to get to annotate toggle now, so i have to place annotation use the ctrl to que it, then close the blue bar to turn off annotations, the toggle it off so i can click through my app then turn back on the annotations and repeat... you guys just keep digging the hole in bad ui design for something that had no issues before.. serious just stop trying to make things "better"