Install an agent CLI
Install the agent CLI on the machine that will execute it.
Before you start
Choose an enabled harness and a target node. Use the OS account that runs the server or node daemon. That account needs access to the CLI, its provider credentials, and the project's files.
Install and check
- Follow the installation instructions linked from the agent's guide.
- Authenticate the CLI with its provider on the target machine.
- Run the CLI directly under the execution account to verify it opens.
- In the server dashboard's sidebar, choose Nodes, select the execution machine, and open Overview. In its Harnesses card, select Re-check.
- Launch a test subshell in an existing directory.
For supported installable harnesses, an administrator can request installation on the server host. This executes the vendor installer as the server's OS user. Install CLIs yourself on remote nodes.
Binary detection
Plugins declare a binary name, known paths, and an optional environment override such as CLAUDE_PATH. Detection runs on the selected machine and is requested by the control plane.
See Files and paths for configuration locations and how foreground and service environments differ before setting a binary override.
A service may have a different PATH from an interactive terminal. If manual CLI launch works but detection fails, inspect the service's runtime environment and the plugin's binary override.
Next steps
Read Agent and launch errors or MCP configuration.
Edit on GitHubLast updated on
