Troubleshooting field guide
Return to a healthy official Codex state, collect precise evidence, then use the original project’s current support channel.
Do not share API keys, auth.json, relay tokens, private conversations, or unreviewed full configuration files in a public issue.
Each check keeps the official app baseline separate from the third-party theme session.
Start by restoring the default appearance and launching Codex normally. Confirm the official app works, then check whether your Dream Skin version matches the latest upstream source. A normal Codex launch does not open the theme CDP session; use the project launcher only after the base app is healthy.
Confirm the selected file is still available in the project-managed theme library and meets the current format, size, dimension, and pixel limits. Reimport a pure JPG, PNG, or WebP through the documented platform control. Do not use a UI screenshot as the background.
Move the focal point away from text, choose a calmer source, strengthen the overlay, or increase panel opacity. Check muted labels and keyboard focus rings, not only headings. Restore if native controls are difficult to use.
Restore first and test the official app. Then review recent upstream commits and issues for compatibility changes. Do not keep injecting an old theme version into a changed renderer.
Verify that the source came from the original repository and compare the exact message with the current macOS README. Do not disable Gatekeeper globally or recursively strip security metadata based on an unrelated post.
Run the command from the original repository’s windows directory. Confirm PowerShell 5.1 or later, Node.js 22 or later on PATH, the registered OpenAI.Codex Store package, and that Codex is closed for installation.
Stop repeated attempts if a process-identity or configuration check aborts. Preserve state and logs, compare your installed version with the current upstream scripts, and use the original issue template.
Reduce the problem to a short sequence from a known base state. Record versions, installation method, exact error, sanitized logs, and numbered steps. State whether normal Codex works after restore.
A maintainer can act faster when the report starts from a known state and contains exact, sanitized evidence.
Operating system:
Codex version and source:
Theme tool version or commit:
Installation method:
Exact error:
Relevant sanitized logs:
Reproduction steps:
1.
2.
3.
Does normal Codex work after Restore?:Good to know
Direct answers based on the current project documentation and the limits of an independent community guide.
Use the jonyhunter/Codex-Theme-Hub Issues page on GitHub. Search for the exact error first, then use the repository issue template if the problem is reproducible.
No. Review and minimize logs. Remove API keys, tokens, auth files, private conversations, and unnecessary personal paths before posting.
No. This site provides independent guidance and a local visual preview. It does not connect to your device, run remote diagnostics, or maintain Codex Dream Skin.
Start with a local preview