Theme did not appear after installation
First confirm Dream Skin actually started; installation and launch are separate steps on both platforms.
Check in this order
- Run the platform start or Desktop launcher again.
- Optionally run the verification script and retain its result.
- Confirm Codex is connected to the local CDP port recorded by Dream Skin.
- Inspect the supported state/log directory without publishing sensitive values.
- After a Codex update, compare compatibility before retrying.
If it still fails: If the injection marker or expected renderer targets are missing, restore and check the upstream issues before trying another change.
Background image did not appear
Confirm you selected a pure background asset rather than a preview screenshot containing Codex UI.
Check in this order
- Use a trusted JPG, PNG, or WebP; macOS also supports HEIC and TIFF through its local flow.
- Prefer 2560 × 1440 and reduce unusually large files.
- Keep the prepared file within 16 MB, 16384px per side, and 50 megapixels.
- Re-select the image through Customize on macOS or the tray on Windows.
- Optionally verify and retain a screenshot.
If it still fails: Do not convert or upload the image through this site. If local decoding fails, preserve the source details and consult upstream.
CPU usage is unexpectedly high
Restore to the base appearance first and compare CPU use before assuming the cause.
Check in this order
- Record the OS, Codex version, Dream Skin commit, and affected route.
- Check whether the issue persists after restore and a normal Codex restart.
- Avoid running repeated verification or reload loops.
- Review current upstream performance issues.
If it still fails: The website cannot repair a local performance bug. Share a redacted reproduction only if the issue remains attributable to Dream Skin.
config.toml parsing stopped installation
Complex or multiline TOML may trigger the installer’s safe refusal path. That is a stop condition, not permission to rewrite the file.
Check in this order
- Do not delete, empty, or rebuild config.toml.
- Do not apply a regular-expression rewrite to complex TOML.
- Retain the exact error and note whether the file changed during the operation.
- Use the documented restore or explicit backup recovery path for your platform.
If it still fails: Review the upstream issue with a redacted error. Never publish API keys, Base URLs, MCP secrets, or the full config file.
A large image failed or used too much memory
Resize the source before retrying; very large or unusually compressed images can consume excessive decode memory.
Check in this order
- Export a 2560 × 1440 master when practical.
- Use a common, trusted image format.
- Reduce file size and keep the prepared asset under 16 MB.
- Keep dimensions under 16384px per side and 50 megapixels.
- Avoid files from unknown or suspicious sources.
If it still fails: If the file still fails locally, do not upload it to this site. Record only non-sensitive dimensions, format, and size for upstream diagnosis.
The layout broke after a Codex update
Restore first. Dream Skin targets a changing desktop renderer, so an app update can require upstream compatibility work.
Check in this order
- Run the platform restore workflow.
- Compare the Codex update date with the current upstream release notes.
- Check the upstream repository for a newer compatible release.
- Reinstall only after reviewing the new scripts and changes.
If it still fails: Do not patch WindowsApps, app.asar, the macOS app bundle, or signatures as a temporary workaround.
Diagnostic report template
Remove usernames, API keys, Base URLs, tokens, private project paths, and personal images before sharing any report.
Platform:
OS version:
Codex version:
Dream Skin commit/version:
Theme:
Install or start command used:
Verification command result:
Expected:
Actual:
Reproduction steps:
Sensitive values removed: yes/noOnly share the minimum information needed to reproduce the issue.