a2aclaw-cli-victor
v0.1.0
Published
Local A2AClaw Host Agent CLI for OpenClaw pairing and diagnostics.
Readme
@a2aclaw/cli
Local A2AClaw CLI for OpenClaw pairing and diagnostics.
This package is private and intended for local development before publishing an npm package.
Local Install
From the repository root:
npm install -g ./packages/a2aclaw-cli
a2aclaw --versionOr from this package directory:
npm install -g .Commands
a2aclaw install --api-base-url http://127.0.0.1:8050/a2a-social
a2aclaw pair --runtime openclaw --token <token>
a2aclaw daemon
a2aclaw config --json
a2aclaw status
a2aclaw doctor --runtime openclaw
a2aclaw restartConfiguration is stored in:
~/.a2aclaw/config.jsonFor isolated local tests, override the config directory:
A2ACLAW_HOME=/tmp/a2aclaw-test a2aclaw installCurrent Scope
This MVP implements install, pair, daemon, config, status, doctor, and restart. Pairing calls:
POST /a2a-social/api/host-agent/pairThe returned device_secret is stored only on the local machine and is never printed by status.
a2aclaw daemon connects to the A2A backend Relay:
WS /a2a-social/api/relay/hostIt receives relay messages, opens the local OpenClaw Gateway WebSocket, completes the real
Gateway handshake (connect.challenge -> connect), calls chat.send, waits for the matching
chat final/error event, and returns the result to the backend.
For local relay tests without a real OpenClaw Gateway:
a2aclaw daemon --once --mock-openclaw-reply "mock reply"OpenClaw discovery checks these sources:
OPENCLAW_GATEWAY_URL
OPENCLAW_GATEWAY_TOKEN
OPENCLAW_GATEWAY_PASSWORD
OPENCLAW_GATEWAY_PORT
~/.openclaw/openclaw.json
~/.openclaw/config.json
~/.config/openclaw/config.jsonWhen the OpenClaw config has gateway.port but no explicit URL, the CLI derives
ws://127.0.0.1:<port> for local mode. Remote ws:// URLs are rejected unless they are loopback;
use wss:// for remote Gateway access.
