Skip to content

Agent CLI not detected

What to do when AgentDock can't find an agent's executable on your system.

AgentDock detects each agent CLI by searching your PATH (plus a few known install locations on Windows and macOS). When detection fails, you'll see an error along these lines:

text
"claude" not found or not runnable on PATH (searched N directories, M path/extension combinations...)

Codex has its own, more specific message, since it's resolved through a dedicated runtime resolver rather than a plain PATH search:

text
Could not locate a working Codex executable. AgentDock's bundled Codex runtime was not found
or did not respond, and no standalone Codex installation was found. Reinstall AgentDock, or
install Codex from https://github.com/openai/codex and set its executable as a custom path
in Settings → Agents.

How to fix it

  1. Confirm the CLI actually runs from a regular terminal: claude --version, codex --version, or agy --version.
  2. Open Settings → Agents and use the Test action for that agent — it reports every path/extension combination AgentDock checked, which is the fastest way to see why detection failed.
  3. If the CLI is installed somewhere non-standard, set a custom executable path override on that agent's row instead of relying on PATH detection.

Warning

On Linux, AgentDock only searches PATH — there is no known-install-directory fallback like on Windows/macOS. Make sure the CLI's install location is actually on your shell's PATH.

Related