Codex desktop: one remote worker request can create duplicate workers in continuous voice

Summary

In a continuous voice conversation in the Codex desktop app, creating one remote project worker resulted in multiple simultaneous duplicate worker sessions with the same prompt and source conversation.

Why this matters

The duplicated workers targeted the same live environment. That creates a risk of concurrent, conflicting changes even when the coordinator intended a single write owner.

Observed behavior

• The coordinator created one remote worker for a project-bound task.
• The creation call initially returned one worker.
• The thread list then showed several active workers created at the same time with identical task content.
• Stop messages sent to the redundant workers were also delivered repeatedly.
• Remote worker monitoring/status calls subsequently became unreliable, including a coordinator wait operation that was unavailable and later status reads that stalled.

Expected behavior

A single worker-creation request should create exactly one worker, and coordinator-to-worker messages should be delivered once. Monitoring should remain available so the coordinator can confirm terminal state.

Environment

• Codex desktop app on Windows
• Continuous voice conversation
• Remote project worker

Reproduction guidance

1. Start a continuous voice conversation.
2. Ask the coordinator to create a single remote worker for a project task.
3. Inspect the thread list immediately after creation.
4. Observe whether more than one identically prompted remote worker appears.

I can provide additional sanitized diagnostics if useful.