Skip to content

Codex VS Code extension: submitted prompts get stuck, disappear, or remain as pending #50653

Description

@merbin2012

What version of the IDE extension are you using?

26.930.31730

What subscription do you have?

ChatGPT Pro 100

Which IDE are you using?

VS Code

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

I am frequently experiencing an issue in the Codex VS Code extension where submitted prompts do not reliably execute.

The issue appears in several ways:

  • I type a prompt and press Enter or click Send. The text disappears from the input box, but the prompt is not added to the conversation and does not execute.
  • Sometimes a loading/spinner icon appears and remains there, but nothing happens even after waiting.
  • Sometimes the prompt executes normally, but the same prompt also appears again as a pending prompt above the input area.
  • Sometimes a prompt that has already executed appears again above the textarea as though it is still pending.
  • In some cases I cannot continue the conversation because the next prompt remains stuck.
  • It happens more frequently after continuing the same conversation for some time, and I especially notice it from my second chat onward.

There is usually no visible error message.

Because of this, I cannot tell whether the prompt was received, queued, processing, failed, or completely lost.

This is happening in the Codex extension inside Visual Studio Code on Windows.

Image

What steps can reproduce the bug?

This does not depend on any specific code snippet. It appears to be related to the Codex VS Code extension chat/input UI.

Steps that frequently reproduce it:

  1. Open Visual Studio Code.
  2. Open the Codex extension.
  3. Start a Codex conversation and send a prompt.
  4. Let Codex complete the task.
  5. Continue the same conversation and send additional prompts.
  6. After using the conversation for some time, type another prompt and press Enter or click Send.

One or more of the following may then happen:

  • The submitted prompt disappears without executing.
  • A spinner/loading indicator appears indefinitely.
  • The prompt executes but also remains visible as a pending prompt.
  • An already completed prompt appears again near the input area.
  • The next prompt cannot be processed, so I cannot continue the conversation.

I notice this much more frequently when using a second Codex chat or after continuing a conversation for a while.

The issue is intermittent, so it may not happen on every single submission.

What is the expected behavior?

When I press Enter or click Send:

  1. The prompt should be reliably added to the conversation.
  2. The prompt should execute exactly once.
  3. The submitted prompt should not silently disappear.
  4. A successfully executed prompt should not remain or reappear as a pending prompt.
  5. The input area should become ready for the next prompt after processing completes.
  6. If a request cannot be submitted or processed, Codex should clearly show an error and provide a retry option.

It would also be very useful if the extension clearly showed the request state, for example:

  • Queued
  • Processing
  • Completed
  • Failed

This would make it clear whether a submitted prompt was actually received.

Additional information

This issue is occurring in the Codex IDE extension for Visual Studio Code on Windows.

It is happening frequently enough to significantly interrupt my workflow because I use Codex continuously while working on projects. When a prompt disappears or remains pending, I sometimes have to submit it again, but then there is a risk that the original request may also execute later and cause duplicate actions.

I have attached a screenshot showing one example of the Codex extension being stuck around the prompt/input area.

There is usually no error message shown when the problem occurs.

If useful, I can also provide my:

  • VS Code version
  • Codex extension version
  • Codex model being used
  • Additional screenshots when the issue happens again

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingextensionIssues related to the VS Code extensionwindows-osIssues related to Codex on Windows systems

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions