a1c48b3a84cc.Quick answer
The current upstream documents the official Store-package workflow but not a Windows 11 build-by-build certification. Record Windows, Codex, Node.js, package, and upstream versions; confirm stock Codex works; then run Install, Verify, and Restore without modifying WindowsApps.
What the upstream Windows workflow actually claims
The current upstream workflow targets the official Store-installed Codex desktop application, requires Node.js 22 or newer, discovers the current Appx package dynamically, and documents Install, Start, Verify, update or repair, and Restore. It does not publish a Windows 11 build-by-build certification table. Codex Theme has not independently captured a Windows 11 device result, so this page provides a reproducible checklist rather than a universal supported badge.
Establish the Windows 11 baseline
Record the Windows 11 edition and build, system architecture, Codex version, Store package identity, Node.js version, PowerShell version, and upstream commit. Launch stock Codex and test the same user account before starting the skin. If the official app cannot launch or its package registration is broken, repair that first. Never take ownership of WindowsApps, replace the executable, or edit app.asar to force a theme result.
Use current state after every Codex update
The upstream guardrails say to rerun install and launch after app updates. The scripts rediscover the registered Store package instead of trusting a previously saved executable path. Let the normal launcher find a free loopback port; if a port was explicitly requested and is occupied, keep the fail-closed result. Verify package identity, Browser ID, process start time, and expected renderer markers before accepting the connection.
Verify more than the background
Run the documented verifier with an absolute screenshot path, then inspect Home and a normal Task. Confirm the continuous wallpaper, native composer, sidebar, menus, scrolling, project selector, route changes, and theme marker. Finish by running Restore and reopening Codex normally. Record any PowerShell error with its script name and first useful message, while removing secrets, auth files, relay tokens, and private conversation content.
Completion checklist
- Windows 11 build is recorded
- Official Store Codex opens stock
- Node.js 22+ is confirmed
- Package and port identity pass
- Home and Task pass Verify
- Restore succeeds
Frequently asked questions
Does Codex Dream Skin work on Windows 11?
The current project documents a Windows Store-package workflow, but it does not provide a universal Windows 11 build certification. Verify the exact Windows build, Codex version, Node.js version, package identity, and upstream commit.
What should I do after Codex updates on Windows 11?
Rerun the current upstream install and launch workflow so it can rediscover the registered Store package, then verify Home, a normal Task, native controls, and Restore.
Do I need to edit WindowsApps?
No. The reviewed workflow is designed to preserve the official Store package and signature. Taking ownership of or patching WindowsApps is outside the safe compatibility path.