OpenClaw keeps failing to install Agent-Reach skill (exec/communication errors) — correct install flow?
I'm using OpenClaw on Windows and asked it to install the third-party Agent-Reach skill from https://raw.githubusercontent.com/Panniantong/agent-reach/main/docs/install.md (opens external site). The agent loops through commands, environment checks, and downloads, but every attempt ends in communication/execution errors and it only prints manual installation scripts. What is the correct way to install Agent-Reach, and how do I debug OpenClaw's tool execution failures?
Originally asked on GitHub: https://github.com/Panniantong/Agent-Reach/issues/61
2 answers
The maintainer confirmed this is not an Agent-Reach bug: your OpenClaw agent could not use its
exectool (shell commands), so instead of running the install steps it kept printing manual scripts. He suggested the agent likely lacks sandbox/exec access, or the session hit a communication error loop.First diagnose OpenClaw's exec access:
- Run
openclaw statusto check if the sandbox is healthy. - Ask your agent a simple command like
echo helloto test exec access. - If exec does not work, the OpenClaw sandbox setup needs fixing (see https://docs.openclaw.ai (opens external site)).
Then install Agent-Reach using one of these methods:
Option A — one-liner (requires exec access):
bashcd /tmp && git clone https://github.com/Panniantong/Agent-Reach.git && cp -r Agent-Reach ~/.openclaw/skills/agent-reach && openclaw gateway restartOption B — manual:
git clone https://github.com/Panniantong/Agent-Reach.git- Copy the folder to
~/.openclaw/skills/agent-reach/ - Run
openclaw gateway restart - Verify that
agent-reachappears in your agent's skill list.
The install.md doc in the repo is meant for humans or agents that can run shell commands. Agent Reach itself is just an installer/config tool — once installed, your agent uses the upstream tools (bird, xreach, mcporter, etc.) directly.
Did this work for you?- Run
What a GitHub user tried on GitHub (Didn't work)
Asked OpenClaw to auto-install Agent-Reach by supplying the install.md URL. The agent repeatedly tried commands, environment checks, and file operations, but every attempt ended in exec/communication errors and it only output manual installation scripts.
Source: https://github.com/Panniantong/Agent-Reach/issues/61 (opens external site)
Did this work for you?
Related questions
- How to get LinkedIn and Instagram contacts in Agent-Reach when their APIs are deprecated?
- bird CLI 'fetch failed' on Twitter search in Agent-Reach: proxy not used by Node fetch
- agent-reach Instagram cookies fail: redirected to login / 'Something went wrong'?
- Long Twitter tweets truncated at "Show more" in Agent-Reach MCP — how to get full text?
- agent-reach read: 'invalid choice: read' error — how to actually read a URL?