Paused automation remains running after restart and may continue consuming usage

What issue are you seeing?

A recurring automation appears to stay running after being paused, and the app still shows it as active even after restarting Codex.

Affected automation:

• Name: Daily Passive Bounty Research
• Automation ID: daily-passive-bounty-research

Observed timeline:

• The affected run started on 2026-06-08.
• Logs show startup websocket prewarm timed out before the first turn could use it at 2026-06-08 12:02:25 JST.
• After that, the thread remained stuck with active_turn_status=InProgress.
• On 2026-06-10, I manually set the automation to PAUSED.
• Even after pausing and restarting the Codex app, the UI still shows the automation as running/spinning.
• The stuck thread is not visible in the UI anymore, so I cannot close it from the thread list.
• Usage also appears to keep decreasing, so I’m concerned the stuck run may still be consuming tokens.

Relevant local evidence:

• Automation status in local config is PAUSED.
• Affected thread ID: 019ea52e-39ee-73d1-b374-a683cef8b499
• Related automation prompt thread ID seen later: 019eaa53-721f-7e12-a713-21891c311cb2

Relevant log lines:

• startup websocket prewarm timed out before the first turn could use it
• active_turn_status=InProgress

What steps can reproduce the bug?

1. Create or run a recurring automation in Codex Desktop.
2. Let the automation start a run.
3. In this case, the run appears to hang during startup after a websocket prewarm timeout.
4. Pause the automation after the run appears stuck.
5. Restart the Codex app.
6. Observe that the automation can still appear as running/spinning in the UI even though it is paused.
7. In my case, the original stuck thread was no longer visible in the UI, so it could not be manually closed.

This is the concrete instance I observed:

• Automation: Daily Passive Bounty Research
• Run start date: 2026-06-08
• Pause date: 2026-06-10
• Result: paused automation still appeared active after restart

What is the expected behavior?

• Pausing the automation should stop the active run.
• Restarting the app should not preserve a ghost running state.
• A hidden thread should not remain active or continue consuming usage.
• If a run hangs during startup, Codex should either fail it cleanly or surface a recoverable error state instead of leaving it stuck as InProgress.

Additional information

I’m mainly worried about two things:

1. The run appears stuck in a ghost InProgress state even after pause + restart.
2. Usage seems to keep decreasing, so I’d like confirmation on whether the stuck run is still consuming tokens on the backend.

Extra context:

• I could confirm from local state that the automation itself was set to PAUSED.
• The UI state and the automation state appeared inconsistent.
• I already sent /feedback with the same summary.

If useful, I can also provide the exact local timestamps and thread IDs I checked from the Codex local state/log files.