How to Restore the Default Codex Appearance

Restoring the default Codex appearance should be the first response when a third-party theme stops loading, a Codex update changes the interface, native controls become hard to use, or you simply want to end the local theme session. This guide follows the documentation referenced by the Codex Theme Hub repository, last checked July 17, 2026.

Codex Dream Skin is a third-party project. Codex Theme Hub is not affiliated with OpenAI or the project maintainer. Because upstream behavior can change, compare these steps with the current repository before acting, especially after a new release.

Before you restore

Do not begin by deleting the project’s folders. Restore tooling may need saved state, a base-theme backup, or recorded process identity to reverse the active session safely. Keep the installed engine and logs in place until the standard interface has been verified.

Save unrelated work, then close Codex when the original restore flow asks you to. If you have edited configuration manually, make a separate reviewed backup of only the files you understand. Do not publish that backup: Codex-related configuration and logs can contain private paths, endpoint information, or other sensitive data.

Record enough context to troubleshoot a failure:

Operating system and version.
Codex version and installation source.
Codex Dream Skin version or commit.
Whether the theme was installed from source, a release, or an older checkout.
The exact restore error and relevant sanitized log lines.

Restore on macOS

The current macOS installer creates a Desktop launcher named Codex Dream Skin - Restore.command. Use that launcher. It is the documented path for stopping the saved injector and returning to the official visual state.

The upstream implementation currently records enough process information to avoid stopping an unrelated job. Its README says pause and restore validate the process ID, executable, script path, and start time; if a stop fails, state is preserved and the operation aborts rather than blindly continuing. Configuration backup and restore also require Codex to be closed and use guarded, same-directory replacement.

After the restore launcher completes:

Start Codex through its normal official application entry, not a Dream Skin launcher.
Check the home view, sidebar, project selector, and prompt composer.
Open an existing task and confirm task surfaces no longer show the custom wallpaper or injected visual layer.
Quit and reopen Codex once more to make sure the theme does not reappear after a normal launch.
Keep the Dream Skin state and logs until those checks pass.

If the Desktop launcher is missing, do not guess its full path or delete ~/.codex wholesale. Open the latest macos/README.md in the original repository and review the installed engine at the documented ~/.codex/codex-dream-skin-studio location. Use only a restore command currently documented by the project.

Restore on Windows

The current Windows installer creates a shortcut named Codex Dream Skin - Restore. Use it for the normal restore path. If you are working from the original repository’s windows directory, the source-checked PowerShell command is:

powershell.exe -NoProfile -ExecutionPolicy Bypass -File .\scripts\restore-dream-skin.ps1 `
  -RestoreBaseTheme -PromptRestart

This restores the saved base theme and asks before restarting Codex. The original project currently documents an optional -Uninstall flag that also removes the shortcuts Dream Skin created:

powershell.exe -NoProfile -ExecutionPolicy Bypass -File .\scripts\restore-dream-skin.ps1 `
  -RestoreBaseTheme -PromptRestart -Uninstall

Run those commands only from the reviewed original repository. -ExecutionPolicy Bypass applies to that PowerShell process; it does not make an unknown script trustworthy.

The project also documents -RecoverConfigBackup for a specific case: recovering the complete pre-install config.toml backup when configuration is damaged and ordinary -RestoreBaseTheme is not enough. The script saves the current configuration first. Treat this as a recovery operation, not a routine cleanup option, and read the latest Windows README before using it.

After restore, launch the official Store app normally. Verify the title bar, home view, project navigation, task content, and prompt composer. Quit and reopen the app. If the visual layer returns only when using a Dream Skin shortcut, the normal restore may already be successful; remove shortcuts with the documented uninstall option once you have confirmed the standard path.

When a Codex update broke the theme

An application update can change renderer structure, stacking, route behavior, or native controls. A theme may then fail to load, cover a control, or leave part of the interface styled. This does not automatically mean the official app installation is damaged.

Restore first. Test Codex without the theme. If the official interface works, check the original repository’s recent commits and issues for compatibility changes. On Windows, the current documentation says rerunning the installer rediscovers the registered Store package rather than relying on an old executable path. On macOS, the installer validates the current official app and bundled runtime. In both cases, review updated scripts before reinstalling.

Do not keep retrying an old injector against a changed interface. A clean official state provides a reliable baseline for both troubleshooting and reporting.

Verify that restore is complete

A successful command is not the only signal. Confirm all of these outcomes:

The custom wallpaper and translucent theme layer are gone on the home and task views.
Sidebar, project, title-bar, task-panel, and prompt controls remain visible and clickable.
A normal app launch does not open a loopback theme session.
The app survives a full quit and reopen without the custom style returning.
No restore error remains in the project’s current logs.

If you changed model-provider or API settings separately, do not expect a visual restore to reverse those independent choices. The repository says theming does not automatically rewrite API keys, Base URLs, or model-provider configuration.

If restore does not complete

Stop repeating the command when it reports a validation or process-identity failure. Preserve the state and logs that explain the problem. Compare your installed version with the current upstream source and search the Codex Theme Hub GitHub issues for the exact message.

Create a reproducible report containing the operating system, Codex version, theme tool commit, installation method, exact error, sanitized log excerpt, and numbered reproduction steps. Remove authentication files, API keys, tokens, private conversation text, and unnecessary personal paths.

Use the project’s issue template rather than a third-party support form. Our Codex theme troubleshooting guide can help you organize evidence, but only the original maintainer can confirm current project behavior.

When to return directly to the repository

Go to the original documentation immediately when the restore script has changed since July 17, 2026, you installed from a release with different files, the saved backup is missing, a process-identity safety check aborts, or a Codex update has a known compatibility issue. Avoid invented cleanup utilities and registry edits. A narrow, documented restore is safer and easier to verify than broad deletion.

Once the official appearance is stable, you can decide whether to leave the third-party tool uninstalled, wait for a compatibility update, or review and reinstall the current version. The important result is a normal Codex launch that works independently of the theme tooling.