611c10176a27.Quick answer
The current upstream documents a v1.3.3 current-user Setup for the official Store app but not a Windows 11 build-by-build certification. Record Windows, Codex, package, and release versions; confirm stock Codex works; then install, verify the staged active theme, and restore without modifying WindowsApps.
What the upstream Windows workflow actually claims
The current upstream v1.3.3 workflow targets the official Store-installed Codex desktop application and offers a current-user Setup.exe with a bundled runtime, graphical tray controls, update or repair, and Restore. It also hardens slow first paint, watcher teardown, Store package updates, and active-theme verification. It does not publish a Windows 11 build-by-build certification table. CodexTheme Tools 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, installation path, and upstream release or commit. The ordinary Setup path does not need global Node.js or manual PowerShell; record those versions only for a deliberate source install. Launch stock Codex and test the same user account before starting the skin.
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
Inspect Home and a normal Task. Confirm the continuous wallpaper, native composer, sidebar, menus, scrolling, project selector, route changes, and theme marker. Finish with the tray Restore or Installed apps uninstaller and reopen Codex normally. For a source install only, use its matching verifier and record script errors without secrets or private paths.
Completion checklist
- Windows 11 build is recorded
- Official Store Codex opens stock
- Install path and release are recorded
- Package and port identity pass
- Home and Task pass
- Restore succeeds
Frequently asked questions
Does Codex Dream Skin work on Windows 11?
The current project documents a v1.3.3 current-user Setup workflow for the Store-installed app, but it does not provide a universal Windows 11 build certification. Verify the exact Windows build, Codex version, package identity, active theme, and upstream release; Node.js applies only to source installs.
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.