CLI detection and diagnostics
AgentDock detects provider executables on launch and exposes the exact diagnostics behind that detection so path problems don't require guesswork.
At launch, and whenever you open Settings → Agents, AgentDock searches for each supported provider's executable and reports back what it found — not just whether detection succeeded.
How detection works
- Claude Code and Antigravity — a
PATHsearch, plus a few known install locations on Windows and macOS. Linux detection isPATH-only, with no known-install-directory fallback. - Codex — a dedicated multi-tier resolver rather than a plain
PATHsearch, checked in order: a custom path override, the Codex SDK's own bundled native runtime, then a standalonecodexinstallation. See OpenAI Codex for why Codex needs this instead of a plain lookup.
Diagnostics
Each agent's row in Settings → Agents has a live Test action that re-runs detection against the configured path and reports the resolved path, executable type, and detected version — the same information you'd want when collecting diagnostic information for a bug report. If a CLI you know is installed still isn't found, you can set a custom executable path to override detection entirely.
Note
Packaged builds and a development environment can have different effective PATH values — a CLI that's detected when running from source isn't guaranteed to be detected in a packaged install, and vice versa.