macOS
~/.codex/codex-dream-skin-studio/scripts/restore-dream-skin-macos.sh
The current script stops only the recorded injector when its process identity still matches, removes the themed launch agent, removes the live renderer skin and clears its state. It can optionally restart Codex normally.
--restart-codexcloses and relaunches Codex through the normal path.--restore-base-themerestores saved appearance keys from the upstream backup.--uninstallremoves the Desktop launchers after restoration.
Windows
powershell -NoProfile -File scripts\restore-dream-skin.ps1
The Windows restore script removes the live skin, closes the saved CDP session and reopens Codex normally. Optional flags have different scopes:
-RestoreBaseThemerestores only the saved appearance keys.-RecoverConfigBackupperforms explicit byte-for-byte recovery of a damaged configuration backup.-Uninstallremoves the created shortcuts.
Post-restore verification
- Confirm the theme injector is no longer running.
- Open Codex normally and check Home, Task and Diff.
- Confirm sidebar, project selector, composer, menus, pets, plugins and authentication still work.
- Record any remaining appearance setting before editing configuration by hand.
Frequently asked questions
How do I restore the default Codex theme?
Use the documented Restore script for your platform, then reopen Codex through its normal launch path and verify that the injector and debugging session are closed.
Will Restore delete my Codex conversations or authentication?
The reviewed theme workflow is designed to preserve threads, plugins, pets, authentication, and the official app. Review the exact flags before using optional uninstall or configuration-recovery actions.
What if Restore cannot verify the saved process?
Keep the fail-closed result. Do not kill unrelated processes or bypass identity checks. Close Codex normally, record the error, and compare the current platform guide with the installed upstream commit.