Independent open-source theme studio

Codex Dream Skin

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

Explore Codex Dream Skin themes

Theme preview

Quick start

From source to a verified theme.

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

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 overview

02 · Install locally

Use the workflow for your platform.

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 Windows

03 · Launch and verify

Watch the local bridge connect.

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 checks

04 · Make it yours

Tune the mood, or return to stock.

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 theme

Before starting: install and open the official Codex desktop app at least once.

Open the complete installation guide →
2desktop platforms
127.0.0.1loopback-only CDP binding
0official package files replaced
1 clickto restore the stock appearance

What it is

A theme layer, not a fork.

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

Made to feel expressive. Built to stay legible.

01

Native controls stay native

The sidebar, project picker, suggestion cards, task content, menus, and composer remain the real Codex interface—not a full-window screenshot.

02

Your image becomes the atmosphere

On macOS, choose a wide image and tune accent colors. The project prepares it as a restrained banner and background beneath frosted content layers.

03

The official package stays untouched

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.

04

Restore is part of the design

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

Three clear layers.

The separation between official app, local injector, and visual theme is the core of the project’s trust model.

01

Official application

Codex Desktop launches normally.

The installed app remains the real runtime. Its package and code signature are not rewritten by the theme.

02

Local bridge

CDP connects on loopback.

The injector targets the expected Codex renderer over a local-only debugging port and reapplies after relevant reloads.

03

Visual layer

CSS changes the atmosphere.

Background art, translucency, accents, and decorative details are added while real controls remain above them.

Security boundary, stated plainly

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 →

Before you install

Know what the project does—and what it does not do.

Designed to

  • Theme the official Codex desktop renderer.
  • Preserve native navigation and input controls.
  • Use a local-only CDP endpoint.
  • Back up relevant appearance settings.
  • Offer verification and restore workflows.

Not designed to

  • Patch or redistribute the Codex application.
  • Rebrand Codex as a different product.
  • Act as an API proxy or model provider.
  • Silently rewrite API keys or base URLs.
  • Grant rights to third-party theme artwork.

Frequently asked

Straight answers.

Trust starts with accurate boundaries. These are the questions we would want answered before allowing any tool to customize a desktop application.

Is Codex Dream Skin an OpenAI product?

No. It is an independent open-source customization project and is not affiliated with, endorsed by, or sponsored by OpenAI.

Does it replace the Codex interface with a screenshot?

No. Decorative layers are designed to sit behind or around the live renderer. The native controls remain interactive.

Does it change API keys or model provider settings?

No. The upstream project explicitly separates theming from API configuration and states that it does not silently rewrite API keys or base URLs.

Is local CDP risk-free?

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

One image. One mood. The same real Codex underneath.

Read the installation guide →Inspect the source ↗