Enhanced Theme Guide for macOS
Prepare, use only the pinned Engine source, verify the exact runtime tuple, and complete Restore without inventing missing instructions.
macOS task boundary
This page defines the macOS evidence and decision flow for the independent local Engine. It does not invent a shell command, application path, package name, or permission prompt that is not present in the pinned Engine documentation. Before using any command, confirm that the guide revision matches Runtime SHA a1c48b3a84cc64532196e624fdf33ee1277cb018 and your exact Engine source.
Prepare the Mac
Save work, note the macOS version and architecture, record the Codex build, and close or back up important sessions. Keep one validated theme JSON and one referenced image in a named local directory. Review source rights and available hashes. Do not proceed with FAIL, a hash mismatch, unexpected scripts or executables, nested archives, traversal paths, extra files, or unresolved redistribution status.
Confirm the pinned Engine instructions
Open the independent Engine source and license linked by the approved record. Use only the macOS procedure for the pinned Runtime SHA. The design must provide a clear evidence slot for the exact command or launcher instruction after it is verified upstream; it must not generate a plausible command from a generic macOS pattern.
Apply on a trusted local machine
The Engine launches or connects to Codex through a loopback Chrome DevTools Protocol endpoint and injects CSS or DOM into the local renderer. The debug endpoint does not provide user-level authentication. Keep it on the trusted local machine, do not expose the port, and use the documented theme directory and Apply action for the pinned Engine.
Verify the macOS session
Record macOS version, architecture, Codex build, Engine version, Runtime SHA, theme and artifact hashes, test date, evidence hash, and observed result. A visual match by itself is not enough. Structural PASS and browser preview remain separate. If the exact tuple is absent, show NOT_VERIFIED; if a previously tested build or artifact changed, show REVERIFY_REQUIRED.
Restore on macOS
Follow the pinned Restore action. Confirm that injected content was removed, the themed CDP session and loopback port were closed, and stock Codex reopened without debug flags. Capture recovery evidence against the same platform and build tuple. If any check is unavailable, label it CANNOT_VERIFY rather than stating that recovery completed.
Troubleshooting boundaries
If the Engine cannot start, the endpoint cannot be reached, the theme cannot be read, or Codex does not reopen cleanly, stop and preserve the displayed facts. Recheck the pinned Engine documentation, local permissions, exact versions, file pair, hashes, and whether another themed session remains open. Do not replace missing evidence with a general macOS claim.
Status and independence
A formal VERIFIED_BY_US value is reserved for a complete exact-build evidence record. Reference material is REFERENCE_ONLY and does not authorize redistribution. CodexSkin Tools is an independent project and is not affiliated with, endorsed by, or sponsored by OpenAI.
Record the macOS result without overclaiming
Keep the result beside the exact Mac evidence tuple rather than in a general platform badge. Record which check completed, which input was unavailable, and whether Restore was observed on the same machine and build. If a permission prompt, command, path, or launcher detail is absent from the pinned Engine source, leave that instruction unfrozen and direct the reader back to the verified source instead of filling the gap from a typical macOS workflow.
States
Errors
Frequently asked questions
Where are the exact macOS commands?
They must come from the verified pinned Engine instructions for the stated Runtime SHA. This copy contract does not invent commands, paths, or permission prompts.
What evidence is needed for a macOS runtime result?
Record macOS version and architecture, Codex build, Engine version, Runtime SHA, artifact hashes, date, evidence hash, observed result, and completed Restore evidence.
What if my Codex build differs from the macOS evidence?
Treat runtime behavior as NOT_VERIFIED or REVERIFY_REQUIRED and repeat the documented verification and recovery workflow for the exact build.