Troubleshoot Codex Styler
Resolve Codex detection, connection, theme import, visual compatibility, and restore issues.
Codex is already running
Select Apply and confirm the restart request. Styler sends a normal quit request first. If the Windows package hides instead of closing, Styler then terminates only the verified Codex UI process tree covered by that confirmation.
A theme or companion package is rejected
Run pnpm package:validate and inspect the exact path. Common causes are undeclared assets, missing licenses, remote URLs, unsupported file types, unsafe archive paths, frame/page bounds, or package size limits.
The interface changed after a Codex update
Restore the official interface, then switch to Conservative mode if Enhanced mode did not already fall back. Include the Codex and Styler versions in a GitHub issue, but do not attach personal workspace content or raw diagnostic logs without reviewing them.
Export a redacted compatibility report
Open Settings → Diagnostics & compatibility, run the local checks, preview the report, then export diagnostics.json and summary.txt as a ZIP. Styler excludes content, DOM text, usernames, full paths, and page titles, and never uploads the file. Attach it manually to the dedicated Windows compatibility issue form.