Codex Dream Skin,
explained before you install it.
Codex Dream Skin is a third-party, open-source way to place custom artwork and styling behind the Codex desktop interface. CodexSkin is a separate community project that adds a gallery, browser-based builder, reviewable skin packages, and a local helper.
What Codex Dream Skin actually does
The open-source engine starts the official Codex desktop app with a loopback-only Chrome DevTools connection, then applies CSS and a small decorative layer to the existing renderer. It does not replace the official app bundle, rewrite its signature, or turn a theme package into executable code.
Use native themes unless you need the image layer
Codex's built-in appearance settings are the simplest option for colors, typography, and portable theme values. Dream Skin is for people who specifically want background artwork, custom atmosphere, and a more visual workspace.
- Native appearance: lowest-risk colors and fonts, with no separate engine.
- Dream Skin: background imagery and decorative styling through a local community engine.
- CodexSkin: presets, local previews, data-only packages, and a clearer install-and-restore path.
Install with a restore-first checklist
Review the source and bundled notices, install the helper once, apply one preset, and verify that the dedicated Restore launcher returns Codex to its official appearance. Keep the debugging interface bound to 127.0.0.1 and never accept a visual theme that changes API keys, providers, or remote Base URLs.
Create a custom Dream Skin without uploading your image
The CodexSkin studio decodes your image in the browser, previews Home, Task, and Diff states, and exports a .codexskin package containing artwork, theme JSON, a manifest, and hashes. Image files do not need to pass through a CodexSkin upload API.
Restore before troubleshooting or updating
Codex updates can change private renderer structure and temporarily break community styling. Restore the official appearance first, confirm Codex works normally, then update or reinstall the reviewed engine. This separates a Codex problem from a skin compatibility problem.
- Close the themed session using the provided Restore launcher.
- Confirm the official Codex appearance and controls work normally.
- Update from the reviewed upstream source before applying the skin again.
- Keep your .codexskin package as portable data, separate from the engine.