Windows installation
Install Codex Dream Skin on Windows
Use this independent guide to review the upstream PowerShell workflow for the Store-installed Codex app.
Support and requirements
- Windows with the official Microsoft Store Codex app installed
- Node.js 22 or newer
- PowerShell
- Permission to create Desktop and Start Menu shortcuts
Before you install
Close Codex before installation. The upstream documentation says its installer validates the registered Store package and stops when the official package identity cannot be verified.
Get the files only from the original repository, review the scripts, and open PowerShell in its windows directory. Avoid unofficial download mirrors.
Install the launcher
.\scripts\install-dream-skin.ps1The installer records the existing appearance values, sets the matching base theme, and creates launch and restore shortcuts unless -NoShortcuts is used.
Launch the themed session
.\scripts\start-dream-skin.ps1If Codex is already open without the verified Dream Skin endpoint, close it first. Command-line callers must explicitly add -RestartExisting when they want the script to restart an open window.
Verify the theme
.\scripts\verify-dream-skin.ps1 -ScreenshotPath "$env:USERPROFILE\Desktop\codex-dream-skin.png"Check both the home view and a normal task. A missing hero, native composer, sidebar treatment, or injection marker is a verification failure.
Theme changes on Windows
The current Windows package uses its bundled decorative assets. It does not document the macOS image-picker workflow. Check the repository changelog before following advice from third-party posts.
Restore the official appearance
.\scripts\restore-dream-skin.ps1 -RestoreBaseThemeRestore closes the recorded CDP session, restores saved appearance keys, and reopens the official app. Add -Uninstall only when you also want the shortcuts removed.
Common problems
- If port 9335 is occupied, the normal launcher chooses a free port unless you explicitly requested the occupied port.
- After a Codex update, rerun install and start so the scripts rediscover the current Store package.
- Do not run untrusted local software while the loopback CDP session is active.
- Use GitHub Issues and include the verify output when the theme does not appear.