Computer ACP

Use this skill when a local ACP-capable client should treat a remote machine agent as if it were a local ACP server.

What this does

computer acp serve starts a local stdio ACP bridge. The remote machine stays in the cloud, but the local client speaks ACP to the bridge process.

That means you can point an ACP client at a command like:

computer acp serve <machine> --agent claude --name review

Setup

1. Ensure the CLI exists.

if command -v computer >/dev/null 2>&1; then
  COMPUTER=computer
elif command -v aicomputer >/dev/null 2>&1; then
  COMPUTER=aicomputer
else
  npm install -g aicomputer
  COMPUTER=computer
fi

1. Verify auth.

$COMPUTER whoami || $COMPUTER login

1. Pick a machine and agent.

$COMPUTER ls --json
$COMPUTER agent agents <machine> --json

Start the bridge

$COMPUTER acp serve <machine> --agent claude --name review

Keep that process running. The local ACP client should launch or connect to this command over stdio.

Recommended pattern

• Use one stable machine per bridge.
• Use one stable session name per task thread.
• Prefer a named session like review or debug so reconnects stay simple.
• Use the normal computer-fleet skill if you only need CLI control and not ACP interoperability.

Example

If acpx is installed, a typical shape is:

acpx --agent "computer acp serve <machine> --agent claude --name review" "fix the failing tests"

Limits

• This bridge is for agent chat/session control, not direct filesystem or terminal passthrough.
• If the bridge process exits, the ACP client loses the connection and should reconnect by starting the command again.

Protocol notes

Read [references/acp-flow.md](references/acp-flow.md) for the supported ACP flow and expected behavior.