Reporting Bugs

When you encounter a bug in Codex, capturing error details helps the team diagnose and fix the problem faster. Start with the Troubleshooting guide to rule out common fixes, then use this page to gather the information needed for an effective bug report.

Before You Report

Before escalating, make sure you have already:

1. Tried the closest path in the Troubleshooting guide
2. Checked for updates using How to Update Codex
3. Reviewed the latest release notes to see whether the issue may already be fixed

Opening Developer Tools

Developer Tools give you access to the console, which logs errors and warnings as you use the application.

1. Click Help in the top menu bar
2. Select Toggle Developer Tools

The Developer Tools panel will appear as a sidebar, a separate window, or at the bottom of the screen — all locations work the same way.

Finding Error Messages

1. Click the Console tab in the Developer Tools panel
2. Look for messages color-coded by severity:
   • Red — Errors (these are the most important for bug reports)
   • Yellow — Warnings (usually not critical but sometimes relevant)
   • White/gray — Informational messages

Capturing Errors for a Bug Report

1. Reproduce the issue — perform the action that caused the problem while the console is open
2. Look for red error messages that appear as you trigger the bug
3. Click the arrow next to an error to expand its full details (stack trace)
4. Right-click the error and select Copy to copy the full message
5. Save or paste the error text for your report

What to Include in a Bug Report

A good bug report includes:

• Codex version and extension version
• Operating system
• What you were trying to do
• Error messages from the console (the full red text, including any expanded details)
• Steps to reproduce — exactly what you did before the error occurred
• Expected behavior — what you thought should happen
• Actual behavior — what happened instead
• Screenshots — if the issue is visual, a screenshot helps
• Troubleshooting already attempted — for example updating, restarting, re-importing, or retrying with a smaller test case

Where to Report Bugs

• Discord: Post in our Discord community for quick feedback and to check if the issue is already known
• Translation extension bugs: Open an issue on the Codex Editor extension repository for problems with translation features, importing, exporting, AI, comments, sync, or the editor UI
• Application bugs: Open an issue on the Codex application repository for problems with the app itself — window management, installation, updates, keyboard shortcuts, or platform-specific issues

Tips

• Keep Developer Tools open if you're experiencing intermittent issues — this makes it easier to catch errors as they happen
• Clear the console before reproducing an issue to isolate only the relevant messages (right-click in the console and select Clear Console)
• Check for updates — the issue may already be fixed in a newer version. Use the Updates button in the main menu's Tools section (see How to Update Codex)
• Link to the relevant troubleshooting path when asking for help — this tells the team what you already tried