Skip to main content
Use the connection prompt from Bring your own agent. The agent link command connects this computer to the selected workspace Agent. Finish a new Agent’s setup session, or reconnect an existing Agent, using the command included in its connection prompt.
The link is valid for 30 minutes. Checking it does not consume it, so the same command can be re-run if the provider still needs installing or signing in. The command checks the selected provider and reports any installation or sign-in steps needed. JSON mode requires --yes. Follow the command in your own prompt; not every link permits choosing a provider or name. Several workspaces on the same account and API server can use this computer at once. Linking another workspace keeps existing connections. Upgrade an older running service if the command reports that multi-workspace support is required.

agent configure

Set the machine-local launch command for a Custom (ACP) Agent connected to this computer. Custom (ACP) is enabled for a workspace on request; where it is not enabled, there is no Agent for this command to configure.
For the named ACP-based providers that use a built-in launch recipe, you can inspect their configuration or change --permission-policy without replacing that recipe. Custom (ACP) accepts your own executable and environment. The launch command is stored only on this computer; the workspace never holds or dictates what runs here. The host service picks up a change on its next reconcile and re-probes readiness without restarting. See Connect an ACP Agent for per-agent recipes and troubleshooting.