Codex Dream Skin: Install the Viral Codex Desktop Skin Tool (macOS and Windows)

The skin tool changes what you see in the Codex desktop app without ever opening the app's own installation files. It works through the Chrome DevTools Protocol, the same debugging interface Chromium-based apps like the Codex Electron shell expose for developer tools, and the connection is bound strictly to 127.0.0.1 so nothing outside your own machine can reach it.

On macOS, the installer checks Codex's code signature, Team ID, and CPU architecture before it will attach, and only opens a debug connection once all three match a genuine Codex build. That check is a large part of why the skin tends to keep working across Codex updates: a new release that still passes those checks works with the skin without any file inside Codex itself being touched.

None of this reaches your account settings. There is no code path in the injector that reads or writes your API key or base URL configuration, those stay exactly where Codex's own settings put them, untouched by the skin.

Two helpers keep the setup low-maintenance. On macOS an optional menu bar agent, added through the Install Menu Bar command, re-checks the connection every few seconds and re-applies the look if Codex restarts, so you rarely relaunch anything by hand. On Windows the bridge listens on a fixed local port (9335) and keeps its state in a CodexDreamSkin folder inside your user AppData, which is also where a backup of the original interface is saved. After a Codex update you re-run Start to reattach, Verify to screenshot and confirm the panels rendered, and Restore to roll everything back to the stock interface whenever you want.

The visual layer itself is a stylesheet plus a small renderer script that redraw the sidebar, suggestion cards, and input field, together with a theme file that maps each color. Running the Customize step, or the load-image and switch-theme scripts, rebuilds that theme from an image you point it at. That is how one engine produces the pink, stage black-and-gold, and sci-fi looks from a single code path rather than five separate builds.

Data as of 2026-07-16, based on the project's own documentation at the project's GitHub repository.

This tool is not an OpenAI product, so the fair question is what a stranger's install script is allowed to touch on your machine. Its documentation is specific about the boundary: local CDP injection only, no modification of the Codex .app bundle, app.asar, or WindowsApps package, and no automatic changes to your API key or base URL. That is a narrower footprint than a lot of tools that promise to reskin an app.

It is still a local script with a live debug connection to a running Codex session, and that is real access even when it stays scoped tightly. The project's own advice is to avoid running unfamiliar programs on the same machine while the skin is active, and reading the install script before running it is a reasonable habit for any local automation tool, not just this one.

If something about the skin does not sit right after trying it, the restore step in the installer above hands the interface back to stock Codex in one step, with nothing left over to clean up afterward.