Restore the official Codex appearance

Restore removes the Codex Skin appearance from this computer and returns Codex to the official native state saved before the first Apply. It does not cancel a subscription, delete an account, remove the Plugin, or erase the theme catalog.

Use the Plugin path first when it is available. The separate recovery launcher remains available when the Plugin, network, website session, Pro access, or Plugin cache cannot be used.

What Restore changes

Before the first Apply, Codex Skin saves the native appearance choice exactly as system, light, or dark, together with the related native code-theme setting. Restore writes those saved values back. It does not force every computer to light mode or choose a new default.

Restore also removes the fixed skin marker and the theme background from the supported Codex view. If the official appearance was already active, the result reports that the computer was not themed instead of pretending that a change occurred.

The recovery point lives outside the replaceable Plugin cache. Cancellation, expiry, refund, sign-out, a broken Plugin update, or removal of the Plugin does not take away the local route back.

Restore from the Plugin

Open a Codex task and make a normal request. No theme ID is needed:

Codex Skin, restore the official Codex appearance.

The Restore Skill uses the fixed platform wrapper and one bounded Helper transaction. It does not call a custom server, download an arbitrary Helper, or require current Pro access.

Once Restore starts acting on the current Codex window, leave that window untouched until it reports a result. Do not send a second Restore or theme request to the same operation.

Restart confirmation

Restore may need Codex to close and reopen once so the saved native appearance can settle and be verified. When the result is CS-FLOW-RESTART-001 with action confirm_restart, Codex Skin asks for an explicit yes or no.

Answering yes authorizes the same one-time Helper to own the close, reopen, restore, and visible verification. Do not start a second launch. After Codex returns, ask for local Status. The restart path is successful only when restartKind is restore and restartStatus is completed.

If no reload is needed, the successful structured result contains:

{
  "ok": true,
  "networkUsed": false,
  "loginRequired": false,
  "pluginRequired": false
}

Those fields describe the recovery transaction. They do not mean that every future theme Apply can work without authorization or access checks.

Offline Restore

Use the offline launcher only when the normal Plugin path is unavailable. It runs the recovery engine installed outside the Plugin cache and requires no network, website login, active Free or Pro access, Node, or working Plugin cache.

macOS

Open the fixed recovery launcher for the current user:

~/Library/Application Support/CodexSkin/recovery/restore.command

The path contains spaces, so copy it as one complete path. Do not replace it with a Helper downloaded from a tutorial or another repository.

Windows

Open the fixed recovery launcher for the current user:

%LOCALAPPDATA%\CodexSkin\recovery\restore.cmd

The recovery engine verifies that it is acting on the supported official Codex process. If that identity cannot be confirmed, it stops instead of modifying an unknown application.

Restore never requires you to disable Gatekeeper, SmartScreen, antivirus, or another operating-system protection. Keep the original warning or stable error code if the system blocks the launcher.

Verify the official appearance

Check the visible Codex window after Restore finishes. The skin artwork and fixed theme marker should be gone, and the native appearance should match the saved pre-Apply choice.

For a direct result, verify ok: true and the three false dependency fields shown above. For a reload result, verify restartKind: restore and restartStatus: completed. Status should no longer carry a pending theme selection from before the completed Restore.

Do not treat restart acceptance, a running Helper, or an old success message as proof. Verification belongs to the current result.

When Restore is useful

Restore is the right action when:

• you want to return to the official Codex appearance;
• current Status reports CS-FLOW-ROLLBACK-001 after an Apply or Switch;
• a Codex update leaves you unsure about the current skin state; or
• the Plugin path is unavailable and you want a local recovery action.

Expiry, cancellation, or refund does not force an automatic Restore. Codex Skin does not remotely remove an appearance that is already visible. You may Restore whenever you choose, but a later Pro reapply needs current Pro access.

If Restore fails

Report the stable code and stop. Do not delete the recovery launcher, state, recovery point, or Plugin cache. Those files preserve the safest remaining evidence and fallback path.

Keep private material out of a report. Do not share tokens, cookies, prompts, code, account data, screenshots, or absolute local paths. Troubleshooting lists the safe next checks, and Contact is the private route for account or order help.

After Restore

The Plugin remains installed unless you remove it separately. You can apply a published Free theme again at any time after the next operation passes its authorization and package checks. A Pro theme requires current Pro access for a new download, switch, or reapply.

Continue with Apply a theme, inspect the Plugin, or read why the offline path is part of the safety boundary.

Questions

Does Restore need an internet connection or active Pro access?

No. The recovery engine is designed to work without network, login, current access, Node, or Plugin cache access.

Does Restore cancel my subscription or delete my account?

No. Restore changes the local Codex appearance. Account, payment, subscription, and catalog records are separate.

Will Restore always put Codex in light mode?

No. It restores the exact system, light, or dark choice and related native code-theme setting saved before the first Apply.

Does Restore uninstall the Plugin?

No. The Plugin stays available for a later Apply unless you uninstall it separately.