How do I install the Computer Acp skill?

Run npx skillmds@latest add harivansh-afk/computer-acp in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Computer Acp safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Computer Acp?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Computer Acp free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Computer Acp?

harivansh-afk (@harivansh-afk) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Computer Acp by harivansh-afk — Agent Skill

Name: Computer Acp
Author: harivansh-afk

Computer Acp

Bridge a remote Agent Computer machine agent into a local ACP-compatible stdio process using `computer acp serve`. Use when a local agent client or ACP tool needs to talk to Claude or another remote machine agent through one local command.

harivansh-afk 4c092d4 2 files · 2.9 KB Updated Sep 17, 2026

File contents

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

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

Verify auth.

$COMPUTER whoami || $COMPUTER login

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 for the supported ACP flow and expected behavior.

---name: computer-acpdescription: Bridge a remote Agent Computer machine agent into a local ACP-compatible stdio process using `computer acp serve`. Use when a local agent client or ACP tool needs to talk to Claude or another remote machine agent through one local command.---# Computer ACPUse 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:```bashcomputer acp serve <machine> --agent claude --name review```## Setup1. Ensure the CLI exists.```bashif command -v computer >/dev/null 2>&1; then COMPUTER=computerelif command -v aicomputer >/dev/null 2>&1; then COMPUTER=aicomputerelse npm install -g aicomputer COMPUTER=computerfi```2. Verify auth.```bash$COMPUTER whoami || $COMPUTER login```3. Pick a machine and agent.```bash$COMPUTER ls --json$COMPUTER agent agents <machine> --json```## Start the bridge```bash$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.## ExampleIf `acpx` is installed, a typical shape is:```bashacpx --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 notesRead [references/acp-flow.md](references/acp-flow.md) for the supported ACP flow and expected behavior.

Frequently asked questions