This happens a lot, more or less, over time. Let me know if you need me to dig the specific Codex IDE plugin version, and how to do it. Anyway, the patter is:
After user types in the text field, at the bottom, this Codex chat plugin ‘eats’ the message, it does not move it as a real pending message to the queue.
A test: I tried to copy/paste a richer text from ChatGPT, into the Codex, and then saw the problem, ate/silence.
Then instead, I pasted in the browser urlbar, recopied, and pasted in the chat, and it went through. Could perhaps that be about some characters causing the bug?
You posted this in the appropriate place on the forum for discussing and documenting a Codex bug. The forum, however, is not the official issue tracker. If the problem needs to be formally reported and tracked by the Codex maintainers, the official place is the OpenAI Codex GitHub issue tracker.
Please follow the posting requirements for the Codex Bugs subcategory:
I asked ChatGPT to search for the closest related issue, and it identified:
If that issue describes the same problem you are experiencing, consider adding a reaction to the GitHub issue itself, rather than only reacting to this forum topic. GitHub reactions can help the maintainers gauge how many users are affected.
If it does not match your problem closely enough, search the existing Codex issues for a better match. If you cannot find one, consider opening a new issue and include as much relevant information as possible, such as your Codex version, operating system, environment, reproduction steps, expected behavior, actual behavior, and any relevant logs or error messages.
This bridge between here and there, it’s amazing, thanks. Exactly because all bugs in the world carry on a strong relationship with use cases. I do see, this thread, therefore, as somewhat valid.
A few months ago, I tried to open the plugin code in the Codex to fix, and apparently I fixed but then i realized it didn’t . I will see now, what Sol 6.1 can do for us. Let us see, if I find something meaningful I ping here.
reaction to the GitHub issue itself, rather than only reacting to this forum topic. GitHub reactions can help the maintainers gauge how many users are affected.