Goal auto-continuation does not resume after transient network disconnect

What issue are you seeing?

A long-running active Goal stopped after a transient network disconnect and did not automatically resume after connectivity recovered a few minutes later.

This is a problem for unattended workflows: if a Goal is still active and the failure is a recoverable transport/network interruption, Codex should retry or re-enqueue the next continuation turn without requiring the user to notice and manually type another message.

Steps to reproduce

1. Start a long-running Goal in Codex Desktop.
2. Let the Goal execute unattended.
3. Cause or encounter a temporary network interruption while the Goal is active.
4. Restore network connectivity within a few minutes.
5. Observe whether the active Goal continues automatically.

Actual behavior

The Goal did not continue after network connectivity recovered. The thread remained stopped until manual user intervention.

Expected behavior

For recoverable provider/transport/network failures during an active Goal:

• The persisted Goal should remain active.
• Codex should retry with backoff, or schedule a continuation turn once connectivity/auth is healthy again.
• If automatic retry is intentionally bounded, the UI/logs should clearly say that the Goal is paused and why.
• A transient network disconnect should not permanently strand an unattended Goal that still has work remaining.

Why this matters

The Goal feature is specifically useful for long-running/unattended work. A short network outage that requires manual intervention defeats that use case, especially in overnight or remote workflows.

This report is not asking Codex to ignore non-recoverable failures such as quota exhaustion, approval prompts, or explicit user cancellation. The requested behavior is limited to transient disconnects where connectivity later recovers and the Goal is still active.

Environment

• Product: Codex Desktop
• Platform: Windows
• Exact Codex version: unknown from this side conversation
• Observed date: 2026-06-15

Additional context

The user observed that the network recovered within several minutes, but the active Goal still did not resume. Manual continuation was required.