OpenClaw Relay

Use this when the job is:

• "talk to Molty"
• "relay this into an OpenClaw channel session"
• "use acpx"
• "send this through the gateway via acp"
• "work through a remote OpenClaw bridge over SSH"

Not for team.openclaw.ai: starting or inspecting Roboclaw sessions on the Team server is $team-handoff from openclaw/agent-skills (one Gateway request as Peter through Cloudflare Access; operator values live in ~/.config/openclaw/team-handoff.env).

One skill. Two transports:

1. local
2. ssh

Default to local for direct telephone-game work from the current OpenClaw checkout. Use ssh when the target agent/session lives on another machine.

For Peter's setup, Molty normally lives on the Mac Studio gateway, reached as steipete@steipete-macstudio.local; avoid the mac-studio SSH alias for one-shot relay work because that alias auto-attaches tmux.

Script path: scripts/openclaw_relay.py

Target aliases file: config/session_aliases.json

Mode Selection

Choose local when:

• the user explicitly says acpx
• the target session is on the current machine
• the goal is quick relay or private ask

Choose ssh when:

• the target agent/session lives on another host
• you want a persistent bridge session
• you need async queue/wait/show flows on a remote machine

Defaults

The script avoids baked-in personal paths. Override with env or flags when needed.

• transport: local
• local repo cwd: current working directory
• local acpx repo: <cwd>/extensions/acpx
• ssh host: steipete@steipete-macstudio.local
• remote repo cwd: <remote-home>/clawdbot
• remote acpx repo: <remote-home>/Projects/oss/acpx
• gateway token file: <home>/.openclaw/gateway.token
• control session name: codex-bridge
• target aliases file: config/session_aliases.json

Useful env vars: