VS Code queue repeatedly executes completed task instead of advancing to the next queued item

What version of the IDE extension are you using?

The newest one for VSCode

What subscription do you have?

Pro

Which IDE are you using?

VSCode

What platform is your computer?

Darwin 25.5.0 arm64 arm

What issue are you seeing?

The queue system in the VS Code Codex extension is unreliable during multi-step workflows.

I've consistently observed three related issues:

1. After a queued task completes, Codex frequently begins executing that same completed task again instead of moving to the next queued item.

1. The queue often fails to automatically advance, leaving remaining queued tasks idle until I manually intervene.

1. Queued tasks do not appear to share conversational context reliably. Later tasks behave as though they are unaware of work completed by earlier queued tasks, resulting in repeated analysis and duplicate work.

Overall, the queue behaves more like isolated jobs than a sequential execution pipeline.

What steps can reproduce the bug?

1. Open the VS Code Codex extension.
2. Start a conversation on a repository.
3. Queue multiple related development tasks (3 or more works well).
4. Allow the first queued task to complete.
5. Observe the queue behavior.

Observed behavior:

• The completed task is frequently selected and executed again.
• The next queued item does not begin automatically.
• If the queue does continue, later tasks often appear unaware of previous completed work.

This behavior has occurred repeatedly across multiple sessions.

What is the expected behavior?

The queue should function as a sequential pipeline.

After a task completes, Codex should:

• Mark the task as completed.
• Remove it from the active queue.
• Automatically begin the next queued task.
• Preserve the conversational context and repository state established by previous queued tasks.

Completed tasks should never be re-queued unless explicitly requested by the user.

Additional information

This issue significantly impacts larger development workflows, where queueing multiple dependent tasks should allow Codex to work autonomously.

Because the queue can become stuck repeating completed work or fail to advance, I have to monitor it continuously and manually intervene. This largely defeats the purpose of having a queue for unattended, multi-step coding tasks.

If it helps, I'm happy to provide screen recordings or extension logs to aid reproduction.