macOS desktop gets stuck behind opaque loading/busy overlay while task remains responsive from mobile

What version of the Codex App are you using (from the “About” dialog)?

26.825.41651 (build 7345)

What platform is your computer?

macOS 26.5.1 (25F80), Apple silicon (arm64)

What issue are you seeing?

The Codex desktop app can get stuck indefinitely on its loading/busy screen. The overlay makes the app content opaque and leaves the Mac UI unusable.

This appears to be a desktop UI-state problem rather than a stalled task or backend connection: while the Mac app remains stuck behind the loading/busy overlay, I can open the same Codex task from my phone, send commands, and receive responses successfully. The task continues running/responding remotely, but the Mac app does not recover or dismiss the overlay.

What steps can reproduce the bug?

1. Open an active Codex task in the macOS desktop app.
2. Continue using the task until the app enters its loading/busy state.
3. Observe that the loading overlay remains indefinitely and makes the underlying screen opaque/unusable.
4. From the ChatGPT mobile app, open the same remotely accessible Codex task.
5. Send a command from the phone.
6. Observe that the task accepts and responds to the mobile command while the Mac app remains stuck.

The trigger is intermittent/not yet isolated.

What is the expected behavior?

The macOS desktop app should clear the loading/busy overlay when the task state changes, remain synchronized with remote activity, and recover its interactive UI without requiring an app restart.

What is the actual behavior?

The loading/busy overlay remains stuck indefinitely on the Mac even though the same task is alive and responsive through mobile remote control.

Additional information

The cross-device behavior is the strongest diagnostic signal: mobile commands and responses continue normally, which suggests the failure is in the macOS desktop renderer or local busy-state synchronization rather than in task execution itself.

No logs are attached because they may contain local paths or task content.

Start by reproducing the stuck loading/busy overlay in the macOS desktop app while the same task remains responsive from mobile. Inspect the desktop renderer and local busy-state synchronization around task-state changes; done means the overlay clears, the task stays synchronized with remote activity, and the UI becomes interactive without restarting.