I have been noticing over the latest Codex extension for VS Code updates, that some prompts would not be queued when sent while Codex is working, but after the last update, none will get queued whatsoever, forcing me to wait until the current task gets completed to be able to send a new prompt.
Not sure if this is a bug within the extension, or what the cause for this issue is. I would highly appreciate any sort of help, as it is very annoying, it forces me to copy all prompts before sending them and I cannot queue prompts to keep the extension working in the background.
In searching the Codex issues with ChatGPT, I found that you had already identified the same similar issue:
While you are welcome to discuss Codex issues here, you have already used the preferred venue. OpenAI Codex developers are active in the Codex Issues tab, so that is the best place to report and track this type of problem.
This is a very real issue and represents true data loss. As the user above noted, while Codex is working on a task I would say about 50% of the time if you submit another request, which would normally get queued, it just loses the command completely. In the best case scenario, this is annoying, in the worst case scenario it represents true data loss in the extension as a user who submits information reasonably expects such data to be saved (at least locally).
It’s easy to reproduce on my system, but I haven’t been able to capture any data post the command being issued. It’s so unreliable I have to save every prompt before issuing commands.
VS Code: 1.128.1
Codex Extension Version: 26.707.71524