CodexDockTilePlugin setDockTile crash still present in 26.611.61753 and destabilizes macOS Dock/LaunchServices

Resolved 💬 2 comments Opened Jun 17, 2026 by SparklesKitchen Closed Aug 6, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

Codex Desktop 26.611.61753 build 4008 still ships the crashing Dock tile plugin.

This is a repeat regression that has been reported across multiple recent builds. It is not just a cosmetic Dock issue or a generic "Codex won't open" problem. On macOS, the Codex Dock tile plugin crashes Apple's Dock helper and can destabilize app launching across the machine.

Observed crash signature:

Process: com.apple.dock.external.extra.arm64
Exception: EXC_BAD_ACCESS / SIGSEGV
Symbol: -[CodexDockTilePlugin_com_openai_codex setDockTile:]

The stack shows repeated recursive frames in:

-[CodexDockTilePlugin_com_openai_codex setDockTile:]

Impact:

  • Dock helper crashes repeatedly.
  • Dock / LaunchServices behavior becomes unreliable.
  • Other macOS apps may bounce, hang, or fail to open while policy/launch services are wedged.
  • syspolicyd can spike heavily while the system keeps assessing the modified/broken app state.
  • The only practical workaround has been to remove CodexDockTilePlugin.plugin and remove NSDockTilePlugIn = CodexDockTilePlugin.plugin from Info.plist.

This workaround stops the Dock helper crash, but it modifies the signed app bundle, which then creates more macOS policy/signature problems unless the app is re-signed locally. That is not a reasonable recovery path for users.

Current reproduced build:

Codex Desktop: 26.611.61753 build 4008
macOS: Apple Silicon
Plugin path: /Applications/Codex.app/Contents/PlugIns/CodexDockTilePlugin.plugin
Info.plist key: NSDockTilePlugIn = CodexDockTilePlugin.plugin

Expected behavior:

  • Codex should not crash Apple's Dock helper.
  • Codex should not ship a Dock tile plugin that recursively calls setDockTile: until EXC_BAD_ACCESS.
  • Updating Codex should not make macOS app launching unreliable.
  • Users should not have to remove a signed bundle component and locally re-sign the app to keep their Mac usable.

Requested fix:

  1. Remove or disable CodexDockTilePlugin.plugin from public builds until fixed.
  2. Ship a clean signed build without the crashing Dock tile plugin.
  3. Provide a documented recovery path for users whose Dock/LaunchServices/syspolicyd state was destabilized.
  4. Confirm the update mechanism will not reintroduce the crashing plugin after users manually remove it.

This has been going on across multiple recent builds and makes the Mac unreliable for normal app launching. Please route this to the Codex Mac app team.

View original on GitHub ↗

2 Comments

github-actions[bot] contributor · 2 months ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #27776
  • #27694
  • #28350
  • #28240
  • #28237

Powered by Codex Action

ArthurNie · 2 months ago

I can reproduce this on Codex Desktop 26.611.62324 / build 4028 on macOS 26.5.1 (25F80).

This happens when launching Codex.app directly, with Codex++ not running.

Recent crash report:

  • Process: com.apple.dock.external.extra.arm64
  • Exception: EXC_BAD_ACCESS / SIGSEGV
  • Loaded image: /Applications/Codex.app/Contents/PlugIns/CodexDockTilePlugin.plugin/Contents/MacOS/CodexDockTilePlugin
  • Top frames:
libobjc.A.dylib objc_storeStrong
CodexDockTilePlugin -[CodexDockTilePlugin_com_openai_codex setDockTile:]
CodexDockTilePlugin -[CodexDockTilePlugin_com_openai_codex setDockTile:]
CodexDockTilePlugin -[CodexDockTilePlugin_com_openai_codex setDockTile:]
CodexDockTilePlugin -[CodexDockTilePlugin_com_openai_codex setDockTile:]

Impact observed locally:

  • repeated com.apple.dock.external.extra.arm64 crash reports
  • elevated WindowServer CPU, around 38-43%
  • Codex renderer / GPU / app-server also show sustained CPU activity
  • visible macOS UI lag

Codex++ was previously used as a launcher and may have amplified the issue, but the crash still reproduces after launching Codex.app directly.