Skip to content

fix: keep selected non-Store Codex launch path on Windows - #2892

Closed
MeSouls wants to merge 1 commit into
jlcodes99:mainfrom
MeSouls:fix/keep-selected-codex-launch-path
Closed

MeSouls wants to merge 1 commit into
jlcodes99:mainfrom
MeSouls:fix/keep-selected-codex-launch-path

Conversation

@MeSouls

@MeSouls MeSouls commented Oct 23, 2026

Copy link
Copy Markdown

Summary

Windows switch-and-start was replacing a user-selected portable ChatGPT.exe with the registered Microsoft Store Codex package.

  • Keep an existing unpackaged ChatGPT.exe even when a Store package is registered.
  • Do not treat a failed PE read of that selected file as permission to overwrite it.
  • Still migrate an official legacy Store Codex.exe to ChatGPT.exe, and still refresh a stale Store install of the same package family.
  • Still reject CLI resources\codex.exe, DLLs, and scripts as the desktop entry.
  • Default launch uses the configured unpackaged exe instead of the Store AppUserModelId.

Test plan

  • cargo test explicit_unpackaged_chatgpt_exe_is_not_replaced_by_store_default --lib in src-tauri (Windows)
  • Set Codex launch path to a portable ChatGPT.exe outside WindowsApps, then switch account and start. The saved path must stay on that exe.
  • A missing unpackaged path, or a CLI codex.exe, may still be replaced by the detected Store app.
  • A stale Store path under the same package family may still be refreshed.

Switch-and-start was replacing a user-selected portable ChatGPT.exe with the registered Microsoft Store package.
@MeSouls MeSouls closed this Oct 23, 2026
@MeSouls
MeSouls deleted the fix/keep-selected-codex-launch-path branch October 23, 2026 03:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant