Skip to content

Agent configuration

How to point AgentDock at a specific CLI executable and verify detection.

Each of the three agents has its own configuration entry in Settings → Agents. AgentDock auto-detects each CLI at startup, but you can override that detection per agent if you have a non-standard install.

What you can configure per agent

  • Custom executable path — override automatic detection with a specific path to the CLI binary. Useful if you have multiple installs, a non-standard install location, or the CLI isn't on your system PATH.
  • Test — a live action that re-runs detection against the configured path (or the auto-detected one) and reports back what it found.
  • Diagnostics — the resolved path, executable type, detected version, and which path/extension combinations AgentDock checked along the way. This is the first place to look when a CLI isn't being picked up — see Troubleshooting: agent CLI not detected.
  • Permission mode and model / reasoning effort — also configured per agent; see Permissions and Models.

Tip

If you install or update a CLI while AgentDock is running, use the "Test" action in Settings → Agents rather than restarting the app — it re-runs detection immediately.

For the full settings reference, see Settings → Agents.