Agent skill

OpenClaw Session Relay

Sends a prompt into another OpenClaw agent session over a local or SSH acpx bridge, resolving target sessions from a configurable alias file.

MITAuto-check passedAgent Workflows

Install OpenClaw Session Relay

skills CLI

$ npx skills add steipete/agent-scripts --skill openclaw-relay -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install steipete/agent-scripts openclaw-relay --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/steipete/agent-scripts.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/openclaw-relay .claude/skills/openclaw-relay && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "openclaw-relay" agent skill from https://github.com/steipete/agent-scripts/tree/main/skills/openclaw-relay into .claude/skills/openclaw-relay/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openclaw-relay", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/steipete/agent-scripts/tree/main/skills/openclaw-relay

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add steipete/agent-scripts --skill openclaw-relay -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install steipete/agent-scripts openclaw-relay --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/steipete/agent-scripts.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/openclaw-relay .agents/skills/openclaw-relay && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "openclaw-relay" agent skill from https://github.com/steipete/agent-scripts/tree/main/skills/openclaw-relay into .agents/skills/openclaw-relay/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openclaw-relay", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add steipete/agent-scripts --skill openclaw-relay -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install steipete/agent-scripts openclaw-relay --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/steipete/agent-scripts.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/openclaw-relay .cursor/skills/openclaw-relay && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "openclaw-relay" agent skill from https://github.com/steipete/agent-scripts/tree/main/skills/openclaw-relay into .cursor/skills/openclaw-relay/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openclaw-relay", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/steipete/agent-scripts.git --path skills/openclaw-relay

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add steipete/agent-scripts --skill openclaw-relay -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install steipete/agent-scripts openclaw-relay --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/steipete/agent-scripts.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/openclaw-relay .gemini/skills/openclaw-relay && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "openclaw-relay" agent skill from https://github.com/steipete/agent-scripts/tree/main/skills/openclaw-relay into .gemini/skills/openclaw-relay/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openclaw-relay", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install steipete/agent-scripts openclaw-relay

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add steipete/agent-scripts --skill openclaw-relay -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/steipete/agent-scripts.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/openclaw-relay .github/skills/openclaw-relay && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "openclaw-relay" agent skill from https://github.com/steipete/agent-scripts/tree/main/skills/openclaw-relay into .github/skills/openclaw-relay/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openclaw-relay", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add steipete/agent-scripts --skill openclaw-relay -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install steipete/agent-scripts openclaw-relay --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/steipete/agent-scripts.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/openclaw-relay .opencode/skills/openclaw-relay && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "openclaw-relay" agent skill from https://github.com/steipete/agent-scripts/tree/main/skills/openclaw-relay into .opencode/skills/openclaw-relay/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openclaw-relay", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: openclaw-relay
GitHub stars: 7.3k
Token cost: ~1.3k tokens
SKILL.md length: 466 words
Files: 4 (incl. scripts)
Skills in repo: 45
Repo updated: Oct 4, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Sends a prompt into another OpenClaw agent session over a local or SSH acpx bridge, resolving target sessions from a configurable alias file.

Works in 2 steps: local → ssh
Relaying a prompt into another OpenClaw session on the same machine
SKILL.md covers Mode Selection, Defaults, Quick Start and Async Workflow, plus 4 more sections
Runs Python scripts from its folder; calls python3

What it does

This skill relays a message into an OpenClaw channel session through `acpx`, choosing between two transports: `local`, for a direct relay from the current OpenClaw checkout, and `ssh`, for reaching a session on another machine, such as a Mac Studio gateway. Local is the default for quick private asks on the current machine, while SSH suits a persistent bridge or async queue and wait flows on a remote host.

The bundled `scripts/openclaw_relay.py` reads target names from `config/session_aliases.json` and exposes commands such as `doctor` for a health check, `targets` to list known aliases, `resolve` to look one up, and `ask` to send a private question to a target session. Defaults for the repo path, SSH host, gateway token file and control session name avoid hardcoded personal paths and can all be overridden through environment variables or flags. It explicitly does not cover reaching the separate Team server, which uses a different handoff skill.

When your agent uses it

Relaying a prompt into another OpenClaw session on the same machine
Bridging a message to an OpenClaw session running on a remote host over SSH
Listing or resolving configured OpenClaw session aliases

Example prompts

“Relay this question to the maintainers session over the local acpx bridge.”
“Ask Molty on the Mac Studio gateway whether the build finished, over SSH.”
“Run the relay doctor check and list the configured target aliases.”

Requirements

Python 3
A local or remote acpx checkout
SSH access for the remote transport

Workflow steps

2 steps, taken from the first numbered list in SKILL.md.

local
ssh

What it can do on your machine

Read from SKILL.md and the folder at commit 79150cf. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
- python3
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

OpenClaw Session Relay loads about 1.3k tokens when it runs. Until then it costs about 21 tokens; SKILL.md has 466 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~21
When it runs · the whole SKILL.md, loaded when a task matches: ~1.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from steipete/agent-scripts at commit 79150cf, republished under its MIT licence (© steipete). 466 words, ~1,271 tokens.

Download SKILL.mdSave it as .claude/skills/openclaw-relay/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.

name: openclaw-relay
description: OpenClaw session relay: prompts/posts via local/remote acpx over SSH.

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:

local
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
python3 scripts/openclaw_relay.py send --message "Reply with exactly OK."
python3 scripts/openclaw_relay.py show

Remote host example:

bash

python3 scripts/openclaw_relay.py doctor --transport ssh --host steipete@steipete-macstudio.local
python3 scripts/openclaw_relay.py send \
  --transport ssh \
  --host steipete@steipete-macstudio.local \
  --message "Reply with exactly OK."

Show full SKILL.md (170 more words)Show less

Async Workflow

Queue work and poll the same control session:

bash

python3 scripts/openclaw_relay.py start --message "Work on X and reply when done."
python3 scripts/openclaw_relay.py wait --after-seq <last-seq>
python3 scripts/openclaw_relay.py show

Target Aliases

config/session_aliases.json ships with placeholders. Replace them with real values for your setup.

Example shape:

json

{
  "main": "agent:<agentId>:main",
  "maintainers": "agent:<agentId>:discord:channel:<channelId>"
}

Session Rules

Use these rules when choosing a command:

Want a private reply from a specific session: ask
Want the target session to decide whether to post: publish
Want a guaranteed direct post: force-send
Want blocking continuity with the control brain: send
Want fire-and-forget async: start, then wait and show
Want to stop queued work: cancel

Failure Handling

If relay work fails:

Run doctor.
Run status.
Run show.
If the control session is wedged, run cancel, then ensure, then retry.

If route discovery is uncertain:

Resolve the target first.
Prefer alias or exact session key.
Use a tiny probe ask before sending the real payload.

Output Relay

Return the actual assistant text or delivery result, not shell noise.

For relay tasks, report:

transport used
target session key
whether the route probe/resolve succeeded
final posted or returned result

Files

SKILL.md and 3 other files (scripts) in skills/openclaw-relay of steipete/agent-scripts.

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

Open the folder on GitHubat commit 79150cf

Compare with similar skills

OpenClaw Session Relay next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

OpenClaw Session Relay compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
OpenClaw Session Relay this skillsteipete/agent-scripts	7.3k	—	~1.3k	Automated safety check: Pass	MIT	4 days ago
Orca CLIstablyai/orca	88k	2 repos	~593	Automated safety check: Pass	MIT	today
Paseo Agent Handoffgetpaseo/paseo	20k	1 repos	~606	Automated safety check: Pass	Custom licence	today
MemPalace Task HandoffMemPalace/mempalace	59k	—	~1.9k	Automated safety check: Pass	MIT	yesterday
Agent Manager Fleet TUIYoanWai/agent-manager	578	—	~1k	Automated safety check: Pass	Apache-2.0	today
Seat Continuity and Handovermvschwarz/openrig	6.2k	—	~2.5k	Automated safety check: Pass	Apache-2.0	today

Similar skills

Orca CLI
stablyai/orca
Operate Orca-managed worktrees, folder contexts, terminals, repos, automations, artifacts, skill sharing, worktree comments, and Orca's embedded browser…
88k GitHub starsUsed in 2 repos~593 tokens
Agent WorkflowsAuto-check passed
Paseo Agent Handoff
getpaseo/paseo
Hands off the current task, including context, decisions and failed attempts, to a fresh agent through Paseo by writing a self-contained briefing prompt and launching that agent.
20k GitHub starsUsed in 1 repo~606 tokens
Agent WorkflowsAuto-check passed
MemPalace Task Handoff
MemPalace/mempalace
Creates, hands off, claims, executes and closes agent tasks through the MemPalace logstream, with approval of the exact task before it is recorded.
59k GitHub stars~1.9k tokensUpdated yesterday
Agent WorkflowsAuto-check passed
Agent Manager Fleet TUI
YoanWai/agent-manager
Runs several coding-agent CLIs as real tmux sessions in one terminal UI, color-coded by whether each is working, waiting, idle or blocked.
578 GitHub stars~1k tokensUpdated today
Agent WorkflowsAuto-check passed
Seat Continuity and Handover
mvschwarz/openrig
Separates a stable agent seat's identity from its changing occupant, and records honest, two-part provenance whenever one occupant replaces another.
6.2k GitHub stars~2.5k tokensUpdated today
Agent WorkflowsAuto-check passed
Harness Engineering
10xChengTu/harness-engineering
Set up and improve harness engineering (AGENTS.md, docs/, lint rules, eval systems, project-level prompt engineering) for AI-agent-friendly codebases.
102 GitHub starsUsed in 1 repo~1k tokens
Agent WorkflowsAuto-check passed

Questions about OpenClaw Session Relay

What does OpenClaw Session Relay do?

Sends a prompt into another OpenClaw agent session over a local or SSH acpx bridge, resolving target sessions from a configurable alias file. This skill relays a message into an OpenClaw channel session through `acpx`, choosing between two transports: `local`, for a direct relay from the current OpenClaw checkout, and `ssh`, for reaching a session on another machine, such as a Mac Studio gateway. Local is the default for quick private asks on the current machine, while SSH suits a persistent bridge or async queue and wait flows on a remote host.

When should I use OpenClaw Session Relay?

OpenClaw Session Relay fits situations like: relaying a prompt into another OpenClaw session on the same machine; bridging a message to an OpenClaw session running on a remote host over SSH; listing or resolving configured OpenClaw session aliases.

How do I install OpenClaw Session Relay in Claude Code?

Run `npx skills add steipete/agent-scripts --skill openclaw-relay -a claude-code`. Or copy the skill folder (skills/openclaw-relay in steipete/agent-scripts) into .claude/skills/openclaw-relay in your project. Claude Code loads it when a task matches its description.

How do I install OpenClaw Session Relay in Codex?

Run `npx skills add steipete/agent-scripts --skill openclaw-relay -a codex`. Or copy the skill folder (skills/openclaw-relay in steipete/agent-scripts) into .agents/skills/openclaw-relay in your project. Codex loads it when a task matches its description.

Can I use OpenClaw Session Relay in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add steipete/agent-scripts --skill openclaw-relay -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/openclaw-relay, .gemini/skills/openclaw-relay, .github/skills/openclaw-relay and .opencode/skills/openclaw-relay in your project.

What does OpenClaw Session Relay need to run?

Going by SKILL.md and its folder, OpenClaw Session Relay needs Python for the scripts in its folder and the command-line tools its instructions call (python3). Our summary lists: Python 3; A local or remote acpx checkout; SSH access for the remote transport.

Does OpenClaw Session Relay access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is OpenClaw Session Relay safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does OpenClaw Session Relay use?

OpenClaw Session Relay is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does OpenClaw Session Relay use?

About 1.3k tokens (SKILL.md is roughly 5.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to OpenClaw Session Relay?

Skills that share tags, products or a category with OpenClaw Session Relay: Orca CLI (stablyai/orca, 88k stars), Paseo Agent Handoff (getpaseo/paseo, 20k stars), MemPalace Task Handoff (MemPalace/mempalace, 59k stars) and Agent Manager Fleet TUI (YoanWai/agent-manager, 578 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains OpenClaw Session Relay?

steipete (a GitHub user) maintains it in steipete/agent-scripts, which has 7,313 GitHub stars. The repository holds 45 skills in this directory. The repository was last updated on October 4, 2026.

Source: steipete/agent-scripts on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install OpenClaw Session Relay

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

OpenClaw Relay

Mode Selection

Defaults

Quick Start

Async Workflow

Target Aliases

Session Rules

Failure Handling

Output Relay

Files

Compare with similar skills

Similar skills

More from steipete/agent-scripts

Related

Questions about OpenClaw Session Relay