Skip to content

fix: correct AUMID generation for Windows Store Codex + fallback to direct execution#591

Open
congxb wants to merge 1 commit into
BigPizzaV3:mainfrom
congxb:fix/windows-store-aumid
Open

fix: correct AUMID generation for Windows Store Codex + fallback to direct execution#591
congxb wants to merge 1 commit into
BigPizzaV3:mainfrom
congxb:fix/windows-store-aumid

Conversation

@congxb

@congxb congxb commented Jun 3, 2026

Copy link
Copy Markdown

Summary

Fixes the bug where CodexPlusPlus cannot launch the Windows Store / MSIX version of Codex due to incorrect AUMID generation.

Problem

The function in incorrectly generates the AUMID by splitting the package name and only keeping the identity prefix and publisher ID, losing the version and architecture parts.

Value
package_name
Before (wrong)
After (correct)

Changes

1.

Use full instead of reconstructing from parts:

2.

Add fallback to direct execution when AUMID activation fails:

Verification

Check Result
Codex processes ✅ 9 processes running
CDP port 9229 ✅ Available
CDP bridge
Injected script ✅ Loaded

Related

…irect execution

- app_paths.rs: Use full package_name + '!App' instead of splitting
  to preserve version and architecture in AUMID
- launcher.rs: Match on activate_packaged_app result and fall back to
  direct Codex.exe execution when AUMID activation fails
- This fixes the bug where Windows Store/MSIX version of Codex could
  not be launched by CodexPlusPlus due to incorrect AUMID format

Fixes BigPizzaV3#590
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.

[Windows] Cannot launch Windows Store / MSIX version of Codex — AUMID generation bug

1 participant