Recommended habit
Prefer Restore when you are done theming.
Local loopback CDP is powerful and unauthenticated. The upstream project explicitly recommends restoring when the theme session is no longer needed.
Restore the official appearance
Use the launcher created by the upstream installer. Do not delete random support files while Codex or the injector is running.
- 01Save your work and quit Codex Desktop.
- 02Open Codex Dream Skin - Restore.command from the Desktop launchers created by the upstream installer.
- 03Review the terminal result. Restore should stop the recorded injector only after its PID, path, and start time match.
- 04Reopen the official Codex app normally and confirm that the native appearance has returned.
- 05If the result is ambiguous, stop and consult the pinned upstream README before removing any files manually.
What Restore is meant to change
Restore is the theme exit path, not an account reset or a Codex data wipe.
Stops the theme injector
The recorded injector job is stopped after the upstream identity checks pass.
Returns the native appearance
Codex should launch without the injected background, banner, palette, and frosted theme layers.
Leaves API setup separate
Theme restoration is not a reason to edit API keys, Base URLs, proxies, or model providers.
If Restore does not complete
Capture the exact terminal output, your macOS and Codex versions, and the path you launched. Do not bypass PID or path checks merely to force the process to stop.
- Expected Restore launcher
- ~/Desktop/Codex Dream Skin - Restore.command
Ask with useful evidence
Send the exact error and environment details to DreamSkin Studio. Never include API keys, access tokens, private prompts, or unrelated Codex logs.