[Bug]: Windows junction-backed CODEX_HOME prevents Codex accounts from loading

[pjhsion]

Client or integration

Codex App

Area

Authentication and account pool

Summary

On Windows, when the default %USERPROFILE%/.codex directory is a junction to another volume, the installed OpenCodeX desktop binary cannot canonicalize the effective Codex home during native-profile admission. The Codex account settings endpoint then returns HTTP 500 instead of the configured account list. I expected the existing Codex accounts to load normally.

Reproduction

1. On Windows, make %USERPROFILE%/.codex a directory junction to another local volume (for example, D:/CodexState), retaining a valid Codex home and account pool.
2. Install OpenCodeX 2.66.0 for Windows and launch the bundled proxy without setting CODEX_HOME.
3. Open the Codex account settings view, or call the authenticated GET /api/codex-auth/accounts management route.
4. Observe HTTP 500 with NativeProfileError: The effective CODEX_HOME is not an accessible directory. The related request path can also report an EUNKNOWN filesystem error while probing auth.json.
5. Set CODEX_HOME to the physical junction target and restart OpenCodeX; the same binary returns HTTP 200 and the existing three pool accounts load.

Version

OpenCodeX 2.66.0 (Windows installer)

Operating system

Windows 11 23H2 (10.0.22631)

Provider and model

Logs or error output

NativeProfileError: The effective CODEX_HOME is not an accessible directory. from native profile context resolution, followed by HTTP 500 for GET /api/codex-auth/accounts.

Screenshots and supporting files

Redacted configuration

%USERPROFILE%/.codex is a directory junction to a physical Codex home on another local volume. No tokens or account identifiers are included here.

Checks

• I searched existing issues and documentation.
• I removed secrets, tokens, account details, request credentials, and personal data.

[lidge-jun]

Fixed on dev by #5865, carried in #5901 (merge dd1e327). It ships with the next release.