[macOS] Desktop app becomes unresponsive after a Codex task completes

Open 💬 1 comment Opened Aug 11, 2026 by Liu-Lin-Hai

What version of the Codex App are you using?

ChatGPT desktop app with Codex: 26.803.61601 (build 6396).

What platform is your computer?

  • MacBook Pro (Apple M4)
  • macOS 15.5
  • Apple Silicon / arm64

What issue are you seeing?

After a Codex task completed, the desktop app became unresponsive.

The app did not restart automatically: I manually quit it after the UI stopped responding, then launched it again.

What steps can reproduce the bug?

I do not yet have deterministic reproduction steps.

Observed flow:

  1. Use Codex Desktop normally.
  2. Wait for a local Codex task to complete.
  3. The completed task is shown, but the desktop UI becomes unresponsive.

What is the expected behavior?

The desktop app should remain interactive after a Codex task completes.

Diagnostic observations

The following are sanitized excerpts from the desktop log. Timestamps are UTC.

  • At 2026-08-11T07:23:23Z, the task reached turn-complete.
  • Before and after completion, the app repeatedly logged the following roughly every 10 seconds:
Native pet composition session failed reason=attachment-failed
Native pet material attachment completed attached=false failureReason=system-glass-unsupported
  • At 2026-08-11T07:24:08Z, the app logged:
[IpcClient] Received broadcast but no handler is configured method=ipc-connection-reset
  • At 2026-08-11T07:24:27Z, the browser route window was reported as unavailable and the local app-server transport stopped.
  • After I manually relaunched the app, the same Native Pet retry loop continued.

Additional state-related errors after the relaunch:

maybe_resume_owner_discovery_failed ... timeout
Conversation state not found
Received turn/completed for unknown conversation

I did not find a new Crashpad dump for this incident.

Notes

The Native Pet / system-glass error is correlated with the incident, but I cannot confirm that it is the root cause. I can provide further sanitized diagnostics if needed.

View original on GitHub ↗

1 Comment

Liu-Lin-Hai · 17 days ago

Additional context

At the time, I was working on macOS Space A while Codex was running in Space B. The pet showed a task-complete notification in Space A. After I clicked the pet, macOS switched to Space B, and the Codex desktop app became unresponsive.

This makes the transition from the pet completion notification to the Codex window a likely trigger for the incident.