Codex macOS desktop app infinite-loads after login

Resolved 💬 1 comment Opened Apr 28, 2026 by flsrg Closed Apr 30, 2026

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

26.422.62136 (2180)

What subscription do you have?

Plus

What platform is your computer?

Darwin 25.4.0 arm64 arm

What issue are you seeing?

Summary

Codex macOS desktop app infinite-loads after login.

Local reset did not fix it.

config.toml has no workspace, cwd, root, or path setting.

codex-dev.db only has:

inbox_items
automations
automation_runs

Logs show successful account/config/model/plugin/thread calls with errorCode=null.

But the worker repeatedly logs:

[git-origin-and-roots] Failed to resolve origin for workspace
errorMessage="ENOENT: path does not exist: ~"

Troubleshooting already attempted

Full reinstall
Cleared caches
Removed ~/.codex
Removed ~/Library/Application Support/Codex
Removed ~/Library/Preferences/com.openai.codex.plist
Checked ~/.codex/config.toml; no workspace/cwd/root/path entry
Checked ~/.codex/sqlite/codex-dev.db; only contains inbox_items, automations, automation_runs

Relevant log excerpt

[git-origin-and-roots] Failed to resolve origin for workspace
errorMessage="ENOENT: path does not exist: ~"
errorName=Error
errorStack="Error: ENOENT: path does not exist: ~
    at LY (/Applications/Codex.app/Contents/Resources/app.asar/.vite/build/worker.js:109:9104)
    at ZZ.getStableMetadata.promise (/Applications/Codex.app/Contents/Resources/app.asar/.vite/build/worker.js:126:6186)
    at ZZ.getStableMetadata (/Applications/Codex.app/Contents/Resources/app.asar/.vite/build/worker.js:61:14309)
    at ZZ.getRepoRepository (/Applications/Codex.app/Contents/Resources/app.asar/.vite/build/worker.js:126:5410)
    at ZZ.getWorktreeRepository (/Applications/Codex.app/Contents/Resources/app.asar/.v

What steps can reproduce the bug?

Install Codex desktop app on macOS.
Launch the app.
Log in successfully.
App remains stuck on infinite loading.
Logs continue to show successful app-server calls, but also ENOENT: path does not exist: ~.

What is the expected behavior?

The Codex desktop app should finish loading and show the workspace/thread UI, or show a recoverable error if a workspace path is invalid.