codex - 💡(How to fix) Fix Codex macOS desktop app infinite-loads after login [1 comments, 2 participants]

[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

TL;DR

The issue is likely caused by a missing or invalid workspace path, and setting a valid workspace or root path in the config.toml file may resolve the infinite loading issue.

Guidance

• Verify that the config.toml file has a valid workspace or root path setting, as the error message suggests that the path ~ does not exist.
• Check the logs for any other error messages that may indicate a specific issue with the workspace or path configuration.
• Try setting a valid workspace path in the config.toml file, such as workspace = "/path/to/valid/workspace", and restart the app to see if it resolves the issue.
• If the issue persists, try resetting the app to its default configuration by removing the config.toml file and restarting the app.

Example

No code snippet is provided as it is not clearly supported by the issue, but an example of a valid config.toml file with a workspace path setting could be:

workspace = "/path/to/valid/workspace"

Notes

The issue may be specific to the macOS platform, and the solution may not apply to other platforms. Additionally, the codex-dev.db file only contains limited data, which may indicate a larger issue with the app's configuration or data storage.

Recommendation

Apply workaround: Set a valid workspace or root path in the config.toml file, as this is the most likely cause of the issue and is a simple configuration change to test.