Codex binary path stuck on stale value; app keeps checking /Users/username/bin/codex even after reset

[chindris-mihai-alexandru]

Summary

T3 Code keeps reporting Codex CLI (/Users/username/bin/codex) is not installed or not executable even after resetting codex overrides, clearing the app data, and explicitly setting a valid binary path. The app appears to persist or rehydrate a stale codexBinaryPath value and never falls back to PATH.

Steps to reproduce

1. Install Codex CLI via npm/Homebrew (works in terminal: codex --version).
2. Open T3 Code and set Codex binary path (or reset overrides).
3. Quit the app, clear app data, reopen.
4. The app still reports Codex CLI (/Users/username/bin/codex) is not installed or not executable. even though /usr/local/bin/codex and /opt/homebrew/bin/codex are valid.

Expected

• If the configured binary path is missing/unusable, fall back to PATH (codex).
• Resetting overrides should clear any stale paths.

Actual

• App consistently checks /Users/username/bin/codex and fails, even after reset.

Environment

• macOS Tahoe 26.3.1
• Codex CLI installed via npm/Homebrew

Notes

This looks related to earlier reports about codexBinaryPath not being honored (#486) and Homebrew detection issues (#777). It seems the stale path is sticky and never replaced by PATH or the newly set value.

[chindris-mihai-alexandru]

Update: Even after resetting settings/app data, the desktop app keeps surfacing Codex CLI (/Users/mihai/bin/codex) is not installed or not executable in the server logs during session start. The binary is valid and spawnSync('/Users/mihai/bin/codex', ['--version']) succeeds in a normal Node/Electron environment. This suggests the app’s persisted codexBinaryPath remains stale or is rehydrated despite resets. A fallback to PATH when the configured path fails would unblock users.