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 JSON file (codux-diagnostics-<timestamp>.json) with a redacted snapshot we can use:

• App and update info
• Key paths (app support dir, runtime temp dir, runtime log, live log)
• Redacted settings, your project list, and AI state
• A performance snapshot (recent main-thread stalls)
• Redacted SSH profiles and basic environment (OS, architecture)

Attach this JSON to your GitHub issue. Note it records the paths of your log files, not their contents — attach the log files themselves if we ask.

Log files

Codux writes two logs:

• runtime-rust.log — the main runtime log, in the app data directory
• live-rust.log — the live runtime bridge, in the system temp directory

Platform	App data directory	Temp directory
macOS	~/Library/Application Support/Codux	$TMPDIR/codux
Windows	%APPDATA%\Codux	%TEMP%\codux
Linux	~/.config/Codux (or $XDG_CONFIG_HOME/Codux)	/tmp/codux

So on macOS the two files are ~/Library/Application Support/Codux/runtime-rust.log and $TMPDIR/codux/live-rust.log.

Codux clears the runtime log at the start of each session; older runs are rotated to runtime-rust.log.1 … runtime-rust.log.5. Open the app data folder on macOS with:

open ~/Library/Application\ Support/Codux

Crash reports (macOS)

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

open ~/Library/Logs/DiagnosticReports

Issue checklist

When opening an issue, please include:

• OS version + Codux version
• Reproduction steps
• The diagnostics JSON (Help → Export Diagnostics…)
• runtime-rust.log (and the rotated runtime-rust.log.1 if relevant)
• live-rust.log if present
• A matching crash report (if any)