Codex Dream Skin safety model
Understand the safety boundary before installing a third-party Codex appearance tool.
Short answer
Dream Skin connects only to Codex on your own computer. Other devices cannot use that connection, but other programs running under your account may be able to reach it while the theme is active, so use trusted local software and restore when finished.
Separate data from executable code
A theme pack is data: theme.json plus an image. Install, start, tray, styling, and restore scripts are executable code. Get those scripts from the named Codex Dream Skin GitHub project and avoid opaque repackaging.
Keep the official app intact
Codex Dream Skin checks the official app and applies styles while it runs. It does not need to replace the application bundle, WindowsApps files, app.asar, or the code signature.
Keep appearance separate from accounts
Theme installation must not alter API keys, auth.json, model providers, Base URLs, proxies, account data, or private conversations.
Close Dream Skin when finished
Codex Dream Skin limits its connection to this computer and checks that it belongs to Codex. Even so, run only trusted local software while using the theme and restore when finished.
Treat artwork rights as a separate check
Software licensing does not grant rights to every bundled or user-provided image. Use artwork you created, licensed, or have permission to redistribute; preserve author and license notices.
Project references
Ready to choose a theme?
Preview artwork and readability before applying anything locally.