No terminal checklist. Tell Codex what the theme should feel like and it can install the right skill, design the artwork and palette, apply the result to the running app, inspect a real screenshot, and export a shareable file. When you are finished, a second sentence returns Codex to its native look.

Two sentences cover the full theme lifecycle

Paste the first prompt to build. Replace the words inside the quotation marks with any subject, era, palette, image, or mood. Paste the second prompt whenever you want the stock Codex appearance back.

01 · Build

Describe it. Codex builds it.

This sentence also grants permission to install a missing skill, generate artwork, apply the theme, and visually verify the live app.

Use $codedrobe-one-shot-theme from https://www.codexskins.org/SKILL.md to create and directly apply a “warm 1970s sci-fi control room” theme for Codex. You may install the missing skill, generate the artwork, verify the result with a real screenshot, and deliver the shareable theme file plus its restore method.

02 · Restore

One sentence back to native.

This explicitly authorizes a full restart when Codex has cached the theme palette, so restore does not stop at an old-looking renderer.

Use $codedrobe-theme-manager from https://www.codexskins.org/SKILL.md to restore the native Codex theme. If a restart is required, you may restart Codex automatically; after it reopens, verify that the theme injection, owned watcher, and computed background colors are all back to native.

Why mention restart? Renderer injection disappears immediately, but Codex can cache host colors in the current process. A complete quit and reopen is sometimes the final restore step.

What happens behind that one sentence

You say one sentencein the Codex chat box

Codex installs the skillnpx skills add … runs itself

DOM snapshotcaptures your real, running UI

Artwork + CSS generatedanchored to that snapshot

Probe → apply → screenshotnot "done" until the live render passes

Theme file exported.codedrobe-theme + restore path

What CodeDrobe is

CodeDrobe is an open-source project (Apache 2.0) that ships installable agent skills for creating and managing reversible themes in Chromium/Electron AI desktop apps — Codex included. Instead of running an external theming engine yourself, you teach Codex the skill and delegate the whole job to it.

The workflow that went viral: a user installed the skill and typed "install this skill, then use it to create a kung-fu women's football theme." Five minutes later Codex had generated the artwork direction, registered a dark ink-wash theme, written the color config with a restore backup, and exported a shareable .codedrobe-theme file.

Manual install (optional — Codex does this for you)

Prefer running things yourself? These are the commands Codex executes behind that sentence:

npx skills add qcrao/codedrobe-one-shot-theme-skill --skill codedrobe-one-shot-theme --global --agent codex --yes

After that, theming is a conversation. Try prompts like "create a cyberpunk night theme for this app and apply it," or point it at an image you like. The same repository now includes finder and manager skills backed by the machine-readable CodexSkins catalog, so an agent can also search, download, switch, verify, and restore themes. The runtime exposes codedrobe probe / apply / verify / restore, keeping every action inspectable and reversible.

Why its results fit so well: snapshot-driven CSS

This is the architectural difference that matters. Pre-written theme engines hardcode CSS selectors against one specific Codex build — the moment OpenAI ships a UI update, selectors miss and you get overlapping text, invisible cards, or stray color blocks (a failure mode the Dream Skin project itself acknowledges in its issue tracker).

CodeDrobe inverts the order: at theme-creation time it captures a privacy-preserving DOM snapshot of your actual running Codex, picks semantic anchors from that snapshot, and only then writes the CSS. It then runs a probe → apply → screenshot → repair loop, and refuses to declare success until the live render passes. Your theme is born already fitted to your exact version — there is nothing to go stale on day one.

Dream Skin vs codex-skill: which one to use?

Dream Skin (the engine behind our gallery) is image-first: you bring a picture, it becomes a full-window atmosphere — banner, background, frosted layers — with pixel-level control. It is the stronger choice when the look you want starts from a specific piece of art.

The codex-skill route is prompt-first: you describe a vibe and let the model design it. It shines when you want quick iterations ("make it warmer", "more contrast"), when you want a shareable .codedrobe-theme file, or when you simply enjoy the elegance of an AI IDE dressing itself. It requires granting the skill a debug port, so read the same security notes that apply to any CDP-based approach.

They compose well: generate a concept with codex-skill, screenshot the result you like, then feed that image to the Dream Skin engine for the full treatment — or the other way around.

Security notes

Like Dream Skin, CodeDrobe works through a local debug interface and keeps changes reversible with backups and a restore command. Restore removes renderer injection immediately and puts the saved host appearance back on disk; if the theme changed Codex base colors, fully quit and reopen Codex before judging the final stock look because the running process can cache the old palette. The same rules apply: ports stay on localhost, restore when done, and only install skills from repositories you have read. Our CDP-safety deep dive covers the threat model in detail.