Repository navigation
Description
Bug description
The ChatGPT desktop application for macOS consistently crashes approximately 2–3 seconds after launch on my primary macOS user account.
The same application works correctly on a newly created macOS user account on the same computer.
The older ChatGPT Classic application also works normally.
The crash persists even after a complete reinstall and resetting the application's local configuration.
System information
- Device: Mac Studio (2023), Apple M2 Ultra, 64 GB RAM
- macOS: 27.2.1 (26B131)
- ChatGPT version: 26.1117.31558 (29513)
- Bundle ID:
com.openai.codex - Architecture: Apple Silicon (ARM64)
Steps to reproduce
- Log in to my primary macOS user account.
- Launch
/Applications/ChatGPT.app. - Wait approximately 2–3 seconds.
- The application crashes before becoming usable.
The issue occurs on every launch.
Repeating the same steps on a newly created macOS user account works correctly.
Expected behavior
ChatGPT should launch normally on my primary macOS user account.
Actual behavior
The application crashes with an uncaught Objective-C exception:
NSUnknownKeyException
[NSTaggedPointerString valueForUndefinedKey:]:
this class is not key value coding-compliant
for the key Desktop.
The macOS crash report also shows:
Exception Type: EXC_BREAKPOINT (SIGTRAP)
Foundation:
-[NSObject(NSKeyValueCoding) valueForUndefinedKey:]
-[NSObject(NSKeyValueCoding) valueForKey:]
-[NSObject(NSKeyValueCoding) valueForKeyPath:]
The stack trace involves the Codex Framework and node.napi.armv8.node.
Troubleshooting performed
The following actions did not resolve the issue:
- Completely uninstalled and reinstalled ChatGPT.
- Renamed
~/.codexto force fresh configuration. - Reset application support data in
~/Library/Application Support/com.openai.codex. - Reset application cache in
~/Library/Caches/com.openai.codex. - Isolated the
com.openai.codex.plistpreferences file. - Removed the
NSOSPLastRootDirectorypreference. - Tested without the original
config.toml. - Tested with macOS window restoration disabled.
- Enabled Full Disk Access for ChatGPT.
- Checked Privacy & Security → Files and Folders. ChatGPT does not appear in this list, so Desktop access cannot be enabled there.
None of these actions resolved the startup crash.
Additional log findings
Application logs were collected from:
~/Library/Logs/com.openai.codex/2026/11/20/
The following messages were observed:
Loaded global state from backup
Failed to evaluate or migrate desktop global state
EPERM: operation not permitted
The EPERM message was associated with access to a Google Chrome-related directory.
During multiple startup attempts, the main application log ends shortly after:
[ExecutionPathsService] codex-home request hostId=undefined
These messages may be relevant, but their causal relationship to the crash has not been established.
Diagnostic files
Available for investigation:
- macOS crash report:
ChatGPT-2026-11-20-232146.ips - Application logs:
20.zip(94 log files) - Session transcripts: not available in the preserved
~/.codex-stary/sessionslocation
The full logs and crash report can be provided through a private channel if needed.
Request
Please investigate this reproducible startup crash, particularly user-specific path handling, desktop global-state migration, and macOS Key-Value Coding.
The application works on a fresh macOS account but consistently crashes on my primary account, even after resetting its local data.
I would appreciate a workaround that does not require creating a new macOS user account or losing existing ChatGPT/Codex data.
Activity
github-actions commentedon Nov 20, 2026
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
Czyzzu commentedon Nov 20, 2026
I am experiencing the same crash with ChatGPT 26.1117.31558 (build 29513) on macOS 27.2.1.
The application crashes within 2–3 seconds on my primary macOS account with
NSUnknownKeyExceptioninvolving theDesktopkey.Important diagnostic finding: The exact same application works correctly under a newly created macOS user account on the same Mac Studio (M2 Ultra).
I have already reinstalled the application, reset
~/.codex, Application Support, caches and preferences, and tested Full Disk Access. None of these steps resolved the issue.This suggests a user-profile-dependent startup bug. I can provide the
.ipscrash report and application logs privately if needed.Czyzzu commentedon Nov 20, 2026
20_logs_redacted.zip
Czyzzu commentedon Nov 20, 2026
Workaround: Turning on "Show on all Spaces" in macOS System Settings → Wallpaper fixed the launch crash for me.