Continuous background layer
A selected image can sit beneath native sidebar and main surfaces while route-aware styles keep controls interactive.
Third-party project guide
Codex Dream Skin, explained from the original source.
What it changes, how the two platform paths differ, where to download it, and what to review before enabling a local theme session.
Independent project: Codex Dream Skin is not an OpenAI product. Review the current source, use the original repository, and decide whether its local CDP approach fits your security requirements. No third-party script is completely risk-free.
01 / Features
What the project currently offers.
These points were checked against the original repository at commit a1c48b3 on July 17, 2026 and can change.
Local theme libraries
The current macOS menu-bar and Windows tray flows can import, save, switch, pause, or reapply local themes.
Restore tools
Both platform implementations include a path back to the standard appearance and saved base configuration.
02 / How it works
A local visual layer, not a repackaged app.
The repository describes a local loopback Chrome DevTools Protocol connection. Its scripts identify the official Codex desktop process, start a debug session bound to 127.0.0.1, and inject the theme into expected renderer targets. A small local injector keeps the styles active across route changes.
The upstream documentation says the process does not patch the macOS .app, rewrite app.asar, take ownership of WindowsApps, or change the app signature. It also states that theme configuration is separate from API keys, Base URLs, and model-provider settings.
That design avoids replacing official binaries, but CDP remains a powerful debugging interface. The project documents identity and loopback checks; users still need to avoid running untrusted local software during a theme session and should use Restore when finished.
03 / Setup
Two platforms, two verified paths.
Do not transfer commands between platforms or reuse instructions from unrelated mirrors.
Studio installed in your user profile
The current macOS workflow requires the official Codex desktop app to have been launched once. It validates the bundled runtime, installs the engine under ~/.codex/, stores state in Application Support, and creates launchers for apply, customize, verify, and restore.
PowerShell scripts and a managed runtime
The current Windows workflow requires the registered Microsoft Store Codex app, Node.js 22 or later, and Windows PowerShell 5.1 or later. The installer creates start, tray, and restore shortcuts without requiring WindowsApps ownership.
Open Windows instructions →04 / Safety
Review the boundary before you run it.
- Download source or releases only from jonyhunter/Codex-Theme-Hub.
- Inspect the scripts you plan to run, including changes since this guide was last checked.
- Keep Codex closed when the original install or restore instructions require a stable configuration.
- Do not run untrusted local programs while the loopback debugging endpoint is active.
- Never paste API keys, authentication files, private conversations, or full sensitive logs into public issues.
- Use the provided verify flow and test native navigation, project selection, tasks, and the prompt composer.
This website summarizes upstream behavior and links to the original source. It does not audit every commit, guarantee compatibility, or host a modified installer.
05 / Restore
Keep the way back visible.
On macOS, the installation currently creates Codex Dream Skin - Restore.command. On Windows, the documented restore script supports restoring the base theme, restarting when confirmed, and optionally removing project-created shortcuts.
If a Codex update changes the interface or causes a theme to stop loading, restore first, confirm the official app works normally, then review the latest repository changes before reinstalling. The dedicated restore guide explains the verification steps without inventing unofficial file paths.
Good to know
Project, setup, and safety questions.
Direct answers based on the current project documentation and the limits of an independent community guide.
No. It is an independent third-party open-source project. Codex Theme Hub is also independent and is not the project maintainer.
The repository currently states that its macOS and Windows implementations use a local loopback CDP connection and do not modify the official app bundle, app.asar, WindowsApps, or the code signature.
The current macOS documentation says it validates and uses the signed Node runtime bundled with Codex, so no global Node.js install is required. The Windows documentation currently requires Node.js 22 or later on PATH.
Use the repository and release links maintained by Codex Theme Hub. This website does not host installers, scripts, archives, or mirrors.
Yes, the project documents platform-specific restore scripts or launchers. Review the current restore instructions and verify the native interface after completion.
No. The repository itself notes that CDP is powerful and unauthenticated on loopback. Do not run untrusted local programs while it is active, and restore the standard setup when you are done theming.
Start with a local preview