01 · Get the source
Start with the public project.
Download the current upstream source and review the platform notes before running anything. The project stays inspectable from the first step.
Open the source-backed overviewIndependent open-source theme studio
Codex Dream Skin gives the Codex desktop app a visual identity of your own—without replacing its native interface or modifying the official application package. Choose a mood, keep the real controls, and restore the stock look when you are done.
macOS and Windows · Local loopback CDP · Reversible by design
Quick start
Scroll through one continuous setup story. The Codex window stays in place while each installation state enters, resolves, and hands off to the next.
A live HTML simulation of the documented setup flow—not a command runner and not a replacement for the installation guide.
01 · Get the source
Download the current upstream source and review the platform notes before running anything. The project stays inspectable from the first step.
Open the source-backed overview02 · Install locally
Run the macOS shell workflow or the Windows PowerShell workflow. The installer prepares a local launcher without rewriting the official Codex package.
Choose macOS or Windows03 · Launch and verify
Codex launches with a loopback CDP endpoint, the expected renderer is validated, and the visual layer is applied only after those checks pass.
Review the verification checks04 · Make it yours
Choose restrained artwork and accents, confirm that native controls remain usable, and keep the restore path close whenever the themed session is no longer needed.
Create a custom themeBefore starting: install and open the official Codex desktop app at least once.
Open the complete installation guide →Tutorial library
Platform-specific installation, real theme customization, verification, update recovery, and safe restore—built from upstream documentation and public support issues.
Set up, customize, verify, update, and restore.
↗02 · WindowsPowerShell, Node.js, Store validation, and recovery.
↗03 · DesignChoose readable artwork and balanced accent colors.
↗04 · RecoveryFix stale files, failed verification, and update drift.
↗What it is
We built Codex Dream Skin for people who spend long stretches inside a coding workspace and want that space to feel personal—without pretending the visual layer is the product itself.
The project launches the official Codex desktop app with a local Chromium DevTools Protocol endpoint, validates the expected process and renderer, then injects CSS and small decorative DOM elements. The working interface remains Codex. Your theme supplies the atmosphere.
Read the technical overview →Design principles
The sidebar, project picker, suggestion cards, task content, menus, and composer remain the real Codex interface—not a full-window screenshot.
On macOS, choose a wide image and tune accent colors. The project prepares it as a restrained banner and background beneath frosted content layers.
The scripts do not patch the Codex app bundle, app.asar, WindowsApps files, or the official code signature. The visual layer is applied at runtime.
A theme is only useful when it is reversible. Dedicated restore flows stop the injector, close the debug session, and return Codex to its stock appearance.
The runtime path
The separation between official app, local injector, and visual theme is the core of the project’s trust model.
Official application
The installed app remains the real runtime. Its package and code signature are not rewritten by the theme.
Local bridge
The injector targets the expected Codex renderer over a local-only debugging port and reapplies after relevant reloads.
Visual layer
Background art, translucency, accents, and decorative details are added while real controls remain above them.
Loopback prevents LAN access, but it does not authenticate other processes running as the same local user. Treat the CDP session as sensitive and use Restore when you no longer need the skin.
Read the safety model →Real interface, new mood
The best themes support the interface instead of competing with it: quiet space behind text, deliberate contrast, and enough restraint to keep long sessions comfortable.



Before you install
Designed to
Not designed to
Frequently asked
Trust starts with accurate boundaries. These are the questions we would want answered before allowing any tool to customize a desktop application.
No. It is an independent open-source customization project and is not affiliated with, endorsed by, or sponsored by OpenAI.
No. Decorative layers are designed to sit behind or around the live renderer. The native controls remain interactive.
No. The upstream project explicitly separates theming from API configuration and states that it does not silently rewrite API keys or base URLs.
No. Loopback binding blocks network exposure, but CDP is powerful and has no same-user authentication. Run only trusted local software while a themed session is active, then restore when finished.
Make the workspace yours