openclaw-relay

Files (5)

• SKILL.md
• openai.yaml · agents/
• session_aliases.json · config/
• openclaw_relay.py · scripts/
• test_doctor_token.py · scripts/

SKILL.md (first lines)

# 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:

- `OPENCLAW_RELAY_TRANSPORT`
- `OPENCLAW_RELAY_HOST`
- `OPENCLAW_RELAY_CWD`
- `OPENCLAW_RELAY_ACPX_REPO`
- `OPENCLAW_RELAY_GATEWAY_URL`
- `OPENCLAW_RELAY_GATEWAY_TOKEN_FILE`
- `OPENCLAW_RELAY_SESSION`
- `OPENCLAW_RELAY_TARGETS_FILE`

## Quick Start

Health check:

```bash
python3 scripts/openclaw_relay.py doctor
```

List known target aliases:

```bash
python3 scripts/openclaw_relay.py targets
```

Resolve a target alias:

```bash
python3 scripts/openclaw_relay.py resolve --target maintainers
```

Ask a target session a question privately:

```bash
python3 scripts/openclaw_relay.py ask \
  --target maintainers \
  --message "Summarize the current vibe in this channel."
```

Force-send text to the resolved target:

```bash
python3 scripts/openclaw_relay.py force-send \
  --target maintainers \
  --text "Deploy is done."
```

For multiline posts, use `--text-file <path>` or `--text-file -` instead of
shell-quoting the message.

Force-send media when the user explicitly wants a channel post:

```bash
python3 scripts/openclaw_relay.py force-send \
  --transport ssh \
  --host steipete@steipete-macstudio.local \
  --target maintainers \
  --text "Demo video." \
  --media /tmp/demo.mp4
```

Use the persistent control session:

```bash
python3 scripts/openclaw_relay.py ensure

From steipete/agent-scripts, MIT.

More from steipete/agent-scripts