Collecting diagnostic information
What to gather from AgentDock before filing a bug report.
Before reporting an issue, gather the information AgentDock already surfaces for you — it's almost always enough to diagnose detection, environment, or agent-transport problems.
Settings → Advanced
Open Settings → Advanced (or Open Diagnostics from the Agents tab) for:
- App, Electron, Chromium, and Node.js versions.
- The local SQLite database path.
- Codex runtime resolution details — which detection tier found (or failed to find) a working Codex executable.
Per-agent detection details
On Settings → Agents, the Test action for each agent lists every path/extension combination AgentDock checked during detection — include this output directly if you're reporting a detection issue.
Raw terminal drawer
AgentDock's raw terminal drawer shows the underlying PTY/CLI output directly, including a trace log for debugging. This is the most useful thing to attach when a problem looks specific to one agent's own output rather than to AgentDock itself.
Filing an issue
Include the above, plus your OS/platform and whether you're running a packaged release or a build from source, when opening an issue on GitHub.