I’m experiencing intermittent message loss in the Codex VS Code extension.
- Both long and short typed messages, including messages containing images, sometimes fail to send. The composer clears and the text/content is lost, so the message has to be recreated.
- Some messages appear to submit successfully after a delay, but then disappear from the conversation/queue.
- There is no reliable failure indication when this happens, so it can look as though a message was accepted when it was actually lost.
- VS Code’s built-in Report Extension Issue function cannot be used to report the problem. Selecting Codex – OpenAI’s coding agent produces:
“The issue reporter is unable to create issues for this extension, as it does not specify a URL for reporting issues.”
This makes the failure particularly difficult to report from within VS Code.
Expected behaviour:
Submitted messages should never silently disappear. If submission fails, the composer content should be preserved and an error displayed so the message can be retried.
Messages that are accepted or queued should remain visible and eventually be processed.
The extension should also provide a functioning issue-reporting route from VS Code, or VS Code’s Report Extension Issue function should redirect to the appropriate external reporter.
Reproduction:
- Open Codex in VS Code.
- Use Codex normally over multiple messages.
- Submit messages of varying lengths and/or messages containing images.
- Intermittently, a submitted message clears from the composer without being processed, or appears after a delay and subsequently disappears.
- Attempt to report the problem using VS Code → Report Extension Issue → Codex.
- VS Code reports that the extension has no issue-reporting URL.

I’m experiencing intermittent message loss in the Codex VS Code extension.
“The issue reporter is unable to create issues for this extension, as it does not specify a URL for reporting issues.”
This makes the failure particularly difficult to report from within VS Code.
Expected behaviour:
Submitted messages should never silently disappear. If submission fails, the composer content should be preserved and an error displayed so the message can be retried.
Messages that are accepted or queued should remain visible and eventually be processed.
The extension should also provide a functioning issue-reporting route from VS Code, or VS Code’s Report Extension Issue function should redirect to the appropriate external reporter.
Reproduction: