Fix Windows codex app launcher paths#18530
Merged
etraut-openai merged 1 commit intoetraut/codex-app-x86from Apr 19, 2026
Merged
Fix Windows codex app launcher paths#18530etraut-openai merged 1 commit intoetraut/codex-app-x86from
etraut-openai merged 1 commit intoetraut/codex-app-x86from
Conversation
Open Windows Store URLs through PowerShell while keeping Explorer for shell app targets, since Explorer may return a nonzero status after a successful shell handoff. Normalize extended Windows workspace paths before printing them so users see standard drive and UNC paths after opening or installing Codex Desktop.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This updates the Windows Codex Desktop launcher path handling. Store URLs now open through PowerShell, while shell app targets still use Explorer because Explorer can hand off shell targets successfully while returning a nonzero exit status.
It also normalizes extended Windows workspace paths before printing follow-up instructions, so users see standard drive and UNC paths after opening or installing Codex Desktop.
Validation
just fmtcargo test -p codex-cli