a1c48b3a84cc.Quick answer
The current upstream supports macOS generically but does not publish a macOS 26-specific certification. Record the exact OS, Codex, architecture, and upstream versions; prove stock Codex works; then verify Home, Task, Diff, native controls, and Restore on that same build.
What is currently documented for macOS 26
The current upstream requirements say macOS and document Apple Silicon and Intel workflows, application identity checks, bundled runtime validation, local image themes, Verify, and Restore. They do not publish a macOS 26-specific certification matrix. Codex Theme also does not yet hold a site-owned macOS 26 device capture for this theme workflow. The responsible status is therefore a version-specific checklist, not a claim that every macOS 26 point release and Codex desktop build has been verified.
Prove the official app layer before testing the skin
Record the full macOS 26 point version, Mac architecture, Codex desktop version, install source, and whether stock Codex launches normally. If the official app hangs, opens blank, or fails before the theme launcher runs, troubleshoot that layer first. A theme reinstall cannot establish compatibility when the default application is already unhealthy. Keep those symptoms separate from a theme that connects successfully but only partly styles the renderer.
Test the security and renderer boundaries together
Use the current original repository and note its commit. Confirm the expected signed application identity and bundled Node validation pass. Keep CDP on 127.0.0.1, then verify Home, a normal Task, Diff, navigation, composer, project selection, menus, scrolling, reloads, and route changes. A correct screenshot is not enough if a native control is blocked or the injector attaches to an ambiguous process.
Publish a compatibility result with evidence
A useful result names macOS point version, hardware architecture, Codex version, upstream commit, checked date, install method, the routes tested, and whether Restore returned to the official appearance. Mark a result failed or unverified when any field is missing. After either Codex or Dream Skin changes, rerun the same matrix instead of carrying an old badge forward.
Completion checklist
- macOS 26 point version is recorded
- Codex version and architecture are recorded
- Stock Codex works
- Home/Task/Diff and native controls pass
- Restore succeeds
Frequently asked questions
Does Codex Dream Skin work on macOS 26?
The upstream project documents macOS support, but neither its current requirements nor this site provide a blanket macOS 26 certification. Compatibility must be verified against the exact macOS point release, Codex build, architecture, and upstream commit.
What if Codex itself will not launch on macOS 26?
Test the official app without the theme first. If stock Codex fails, troubleshoot the application or OS layer before attributing the problem to Dream Skin.
What evidence should a macOS 26 compatibility report include?
Include the macOS point version, hardware architecture, Codex version, Dream Skin commit, checked date, install source, routes and controls tested, and Restore result.