Feedback & Diagnostics

Found a bug or have a feature request? Open an issue on GitHub.

The fastest path: Export Diagnostics

Help → Export Diagnostics… saves a single .zip with everything we need:

• Runtime, previous runtime, live, and previous live logs when present.
• Performance summary (recent main-thread stalls).
• Saved app state and invalid-state backups.
• Codex / Claude / Gemini hook/config files and invalid backups when present.
• Up to 12 matching desktop crash / hang / spin reports when available.

Attach this .zip to your GitHub issue.

Manual log collection

If you’d rather collect logs yourself, Codux writes runtime logs to:

• ~/Library/Application Support/Codux/logs/runtime.log
• ~/Library/Application Support/Codux/logs/runtime.previous.log
• ~/Library/Application Support/Codux/logs/live.log
• ~/Library/Application Support/Codux/logs/live.previous.log
• ~/Library/Application Support/Codux/logs/performance-summary.json

Open the folder:

open ~/Library/Application\ Support/Codux/logs

Notes:

• Codux clears the previous session log on each launch.
• runtime.previous.log only appears once the current session log rotates.
• live.log records the live runtime bridge path when available.
• performance-summary.json covers recent performance spikes / main-thread stalls.

Crash reports

If the app crashes or hangs right after launch on macOS, the system may write a crash report to ~/Library/Logs/DiagnosticReports/ (look for Codux-*.ips). Attach the file whose timestamp is closest to the crash.

open ~/Library/Logs/DiagnosticReports

Issue checklist

When opening an issue, please include:

• OS version + Codux version
• Reproduction steps
• runtime.log
• runtime.previous.log (if present)
• live.log / live.previous.log (if present)
• performance-summary.json (if present)
• Matching crash report (if any)