If your Codex skin stopped working, half-applied, or you just want the stock look back before a meeting — this page is the recovery path, in order of least-destructive first. The most common cause by far: a Codex update changed the app's internal renderer, and the skin's selectors no longer match. That's expected for a runtime-injection skin, it's not damage, and it's fixable in a couple of minutes. Nothing here risks your projects or config if you follow the order.
Always work least-destructive → most:
Run Verify (checks skin markers, can screenshot).
Run Restore (returns to stock — non-destructive, reversible).
Re-export / download the latest pack, reinstall, Verify again.
Only then investigate config.
Golden rule: never hand-edit config.toml with a random template to "fix" a skin. Use Restore — it keeps a theme backup and does a clean config round-trip.
Codex Desktop updates can change private renderer structure, so old skin selectors stop matching. Fix: Run Restore → download the newest skin pack → reinstall → Verify. If a fix isn't out yet for a brand-new Codex build, keep the stock appearance until the pack updates. This is normal for any runtime-injection tool and isn't a sign anything is damaged.
Native controls work but the banner/decoration is incomplete → selectors partially stale. Run Restore, reinstall the current pack, Verify. Report the exact Codex version + OS if you file an issue — version-specific detail is what gets it fixed fast.
If Mac reports a missing background file, re-export from the generator or download the current pack — don't create a fake file at the expected path. A known early build (1.1.x) mis-referenced a bundled theme; the current package corrects it.
Stop and run Restore. It restores backed-up appearance settings and does a clean config round-trip. Do not overwrite config.toml with an unrelated template — that turns a cosmetic hiccup into a real problem.
That's a different failure (color theme, not skin). Almost always a bad codeThemeId. Full fix on the dedicated page: Codex theme not showing.
Run Restore (Mac: Restore launcher / command; Windows: restore-dream-skin.ps1).
Delete the skin folder to remove it completely.
Codex returns to its official appearance; your API keys, projects and model settings were never touched by the skin.
The update changed renderer internals; reinstall the latest pack. Nothing is broken.
Yes — Restore is the safe, reversible path. It's designed to be run any time.
No. The skin never reads or writes API keys, Base URL, or project data.
a compatibility fix may not be released yet. Keep stock appearance until the pack updates.