codex-skin.dev

How to Install Codex Dream Skin on Windows (Fix Common Errors)

Overview

Codex Dream Skin applies a reversible renderer skin through Chromium DevTools Protocol while launching the official Store-installed Codex executable. It never replaces or takes ownership of files under WindowsApps, keeping your installation safe and preserving the official package signature.

All native functionality remains intact: sidebar, suggestion cards, project picker, composer, and menus stay fully interactive. Only the decorative banner and background layers are customized.

Prerequisites

Step-by-Step Installation

1. Download the Dream Skin repository

Open PowerShell or Command Prompt and clone the repository:

git clone https://github.com/Fei-Away/Codex-Dream-Skin.git
cd Codex-Dream-Skin\windows

2. Close Codex if it's running

Make sure Codex is completely closed before proceeding. Check Task Manager to confirm no Codex processes are running.

3. Run the install script

Open PowerShell in the windows directory and run:

.\scripts\install-dream-skin.ps1

This script will:

4. Start the skin

Double-click Start Codex Dream Skin.lnk on your Desktop, or run:

.\scripts\start-dream-skin.ps1

The script will:

Note: If Codex is already running, the shortcut will ask before restarting. CLI users must add -RestartExisting flag explicitly.

How to Verify It's Working

After launching, check for these signs:

  1. Custom banner: The Dream-style pink-purple banner appears at the top
  2. Themed background: The task view shows the Dream skin background
  3. Native controls preserved: Sidebar, project picker, and composer buttons work normally
  4. Injection marker: Check the window title or developer tools for the skin marker

You can also use the verification script:

.\scripts\verify-dream-skin.ps1 -ScreenshotPath "C:\path\to\screenshot.png"

The script will check for the hero banner, native composer, sidebar skin, and injection marker.

How to Restore the Official Appearance

Double-click Restore Codex Official Theme.lnk on your Desktop, or run:

.\scripts\restore-dream-skin.ps1

This will:

To also restore the original appearance settings from backup:

.\scripts\restore-dream-skin.ps1 -RestoreBaseTheme

Your configuration, chat history, and authentication state remain untouched.

Troubleshooting

Microsoft Store version shows "Access Denied" error

Symptom: When starting the skin, you see an "Access Denied" or "拒绝访问" error.

Cause: The Store-installed Codex executable has restricted launch permissions that standard paths can't bypass.

Solution: The latest version of the Dream Skin repository includes a fix that uses the shell:AppsFolder method to launch Store apps correctly. To apply the fix:

  1. Pull the latest repository changes: 
    cd Codex-Dream-Skin
git pull
  2. Re-run the install script: 
    cd windows
.\scripts\install-dream-skin.ps1
  3. Start the skin again

If you're already on the latest version and still see this error, check the repository issues for updates.

Windows SmartScreen blocks the script

Symptom: When running the PowerShell scripts, SmartScreen shows a warning like "Windows protected your PC" or "Microsoft Defender SmartScreen prevented an unrecognized app from starting."

Why this happens: The scripts are not digitally signed, so SmartScreen flags them as potentially unsafe.

Solution:

  1. Verify the source first: Make sure you cloned from the official repository (https://github.com/Fei-Away/Codex-Dream-Skin)
  2. Click "More info" in the SmartScreen dialog
  3. Click "Run anyway"

Important: Do NOT disable SmartScreen globally. It's a useful security feature. Only bypass it for scripts you trust from verified sources.

PowerShell shows NativeCommandError or red text

Symptom: When running the scripts in PowerShell 5.1, you see red error text mentioning NativeCommandError or stderr redirection issues, even though the script appears to work.

Cause: PowerShell 5.1 wraps native executable stderr output (like from Node.js) into ErrorRecord objects, causing cosmetic errors that don't reflect actual failures.

Solutions:

After a Codex update, the skin stops working

This is expected. Codex updates may change internal renderer targets or package paths. To fix:

  1. Pull the latest version of the Dream Skin repository: 
    cd Codex-Dream-Skin
git pull
  2. Re-run the install script: 
    cd windows
.\scripts\install-dream-skin.ps1
  3. Start the skin again

If it still doesn't work, check this gallery for compatibility status updates or wait for upstream adaptation.

Node.js not found

Symptom: The script reports that Node.js is not installed or not found.

Solution: Install Node.js 22 or newer from nodejs.org. After installation, close and reopen PowerShell to refresh the PATH, then try again.

The skin appears but some elements look wrong

Check the reference QA inventory in references/qa-inventory.md in the repository to understand expected vs. unexpected rendering. Report unexpected behavior in the repository issues.

Resources: