User impact
Public v1.0.8 on Windows still refuses a saved-account switch with Codex closed. It stops before credential replacement and says GSwitch cannot check Codex configuration, although the selected account can be used elsewhere. The current account remains unchanged. This blocks the main purpose of GSwitch.
Reproduction and evidence
- Install public v1.0.8 and close Codex.
- Keep a saved current account and a usable saved target account.
- Select Switch on the target card.
- GSwitch reports a Codex configuration-check failure before changing the current account.
The maintainer reproduced this with the public installer after PR #124. The screenshot is in the maintainer report; do not attach credentials or raw provider responses.
Current fix
PR #125 prepares v1.0.9. The official installed Codex npm package includes a native Windows executable, while the v1.0.8 App Server launch goes through Node and adds a child process. Repeated attempts left isolated Codex profile directories in GSwitch storage. The PR starts the shipped native executable and distinguishes safe startup, configuration-read, and cleanup failures.
Acceptance
- With Codex closed, the installed public Windows patch can switch to a usable saved target. GSwitch shows the new current identity only after verifying the write.
- The isolated Codex configuration check succeeds without Node in the desktop process PATH and cleans its temporary profile after App Server exit.
- Missing CLI, unreadable configuration, cleanup failure, current credential failure, and target failure have distinct safe English and Chinese messages.
- File-store policy, process checks, current-account protection, rollback, operation lock, and protected recovery remain effective.
- The maintainer verifies switching and account recovery with real accounts before this Issue closes.
Related: account workspace #120.
User impact
Public v1.0.8 on Windows still refuses a saved-account switch with Codex closed. It stops before credential replacement and says GSwitch cannot check Codex configuration, although the selected account can be used elsewhere. The current account remains unchanged. This blocks the main purpose of GSwitch.
Reproduction and evidence
The maintainer reproduced this with the public installer after PR #124. The screenshot is in the maintainer report; do not attach credentials or raw provider responses.
Current fix
PR #125 prepares v1.0.9. The official installed Codex npm package includes a native Windows executable, while the v1.0.8 App Server launch goes through Node and adds a child process. Repeated attempts left isolated Codex profile directories in GSwitch storage. The PR starts the shipped native executable and distinguishes safe startup, configuration-read, and cleanup failures.
Acceptance
Related: account workspace #120.