Support
Start with the local status.
The desktop app can surface runtime health, open its log directory, and export a sanitized diagnostics ZIP.
Quick recovery
- Open Clients and check Codex optimization, proxy, and backend status.
- Use Restart if optimization is running but a local service is unhealthy.
- Use Pause to restore native routing for every managed client while you investigate.
- From Settings, export diagnostics if you need to report an issue.
Diagnostics are sanitized.
The export includes app, OS, runtime, and Codex version metadata, sanitized logs, and redacted Codex configuration. It excludes the activity database, client settings, prompts, request bodies, and credentials.
The export includes app, OS, runtime, and Codex version metadata, sanitized logs, and redacted Codex configuration. It excludes the activity database, client settings, prompts, request bodies, and credentials.
Optional add-ons
Restart the affected client after changing a skill or MCP add-on if its current session does not reload it.
Report an issue
Include the app version, operating system, what you expected, what happened, and the sanitized diagnostics ZIP when appropriate. Review it before uploading, as you would any support bundle.
For release files and notes, use the latest release page.