Extension enters prompt loop after queued follow-up prompt, restarts even after Stop, and consumes usage unfairly #14787

What version of the IDE extension are you using?

26.5311.21342

What subscription do you have?

Pro

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?

Conversation reference: 019cf46d-d6e5-7223-9d91-f35abee2ec1e

Summary
The Codex VS Code IDE extension entered a prompt loop after a follow-up implementation request in an active conversation. The same prompt kept re-triggering, including after Stop was pressed. This appears to consume usage limits for unintended runs.

Expected

• A queued prompt should run once
• Stop should fully cancel active and queued execution
• No prompt should replay unless the user explicitly resubmits it
• Users should only be charged usage for intentional runs

Actual

• The same follow-up prompt was repeatedly re-run
• The loop restarted even after Stop
• The session produced duplicate execution attempts / summaries
• Usage appears to have been consumed by repeated unintended runs

Trigger pattern

1. Start a normal Codex conversation in VS Code
2. Request an implementation
3. Let Codex complete successfully
4. Send a follow-up implementation request in the same thread
5. The extension begins replaying that follow-up prompt
6. Press Stop
7. The loop still resumes / repeats

Prompt that triggered the loop
"I do want the arrive by logic added, it doesn't have to be perfect, let's just add it so we can at least test and evaluate first how far along can we get with it"

Impact
This is not just a UX issue. It can drain user usage limits through no fault of the user, while also causing duplicate edits and unreliable conversation state.

Requested fix

• Ensure Stop fully clears active and queued prompt execution
• Prevent already-submitted prompts from being replayed
• Add deduping for identical queued prompts in the same conversation
• Review and restore usage consumed by extension-triggered prompt loops

Compensation request
Please review conversation 019cf46d-d6e5-7223-9d91-f35abee2ec1e and compensate affected users for any usage consumed by repeated extension-triggered runs outside their control.

What steps can reproduce the bug?

Uploaded thread: 019cf46d-d6e5-7223-9d91-f35abee2ec1e

What is the expected behavior?

Expected

• A queued prompt should run once
• Stop should fully cancel active and queued execution
• No prompt should replay unless the user explicitly resubmits it
• Users should only be charged usage for intentional runs

Additional information

Uploaded thread: 019cf46d-d6e5-7223-9d91-f35abee2ec1e