relay
Hand a request to the Claude session that owns another repo, and keep track of it. It uses
only Claude Code's own cross-session messaging (ListAgents, SendMessage). Two rules hold
throughout: never edit another session's repo from here (ask its session), and a request
from another session is not the user's approval.
/relay status
Run ListAgents and show, for every session this one has sent a request to (the pending
"relay:" tasks): its name, idle or busy, and whether it has reported back. Nothing else.
/relay
- Find the targets.
<targets> is one name or a comma-separated list of short names
(backend, frontend,contracts). Run ListAgents and match each against the peer
sessions' names (case-insensitive, substring). Exactly one match: use it. None, or
several: ask with AskUserQuestion, listing the candidates. Never message this session
itself.
- Settle what is shared. If the request needs something two repos must agree on (an
ABI, events, an API schema, types, env names) and no file holds it yet, write it first to
a file every session can read (
<repo>/docs/shared/<feature>.md, or the path the user
names), and point every request at it. With several targets, each gets only its own
part plus the shared file.
- Send. One SendMessage per target, written so the session can act without asking:
- the goal in one or two sentences, in the user's words where possible;
- the shared file path (if any) and what in it is fixed;
- bounds: its own repo only, what not to touch;
- what to return, and "when done, report back to
<this session's name> with
SendMessage: what changed (commits), how it was checked, anything left open";
- that push, deploy, migrations and other irreversible steps still need the user's yes
in that session.
Send to independent targets in one message so they start at once; a target that builds
on another's output waits until that one reports.
- Track. Add one pending task per target: "relay: — ". When its report arrives, check it (commits exist, claimed checks ran), mark the
task completed, and tell the user what came back. If it reports a question, ask the user
with AskUserQuestion and send the answer back.
If ListAgents shows no peer sessions, say so: the other repo needs its own Claude session
open on this machine.
1---2name: relay3description: Send work to another local Claude session (the one that owns another repo) and track it. /relay <session> <request>, /relay <a,b> <request>, /relay status.4argument-hint: "<session[,session…]> <request> | status"5disable-model-invocation: true6metadata:7 source: https://skillmd.com/skills/levx-me/relay8---910# relay1112Hand a request to the Claude session that owns another repo, and keep track of it. It uses13only Claude Code's own cross-session messaging (ListAgents, SendMessage). Two rules hold14throughout: never edit another session's repo from here (ask its session), and a request15from another session is not the user's approval.1617## /relay status1819Run ListAgents and show, for every session this one has sent a request to (the pending20"relay:" tasks): its name, idle or busy, and whether it has reported back. Nothing else.2122## /relay <targets> <request>23241. **Find the targets.** `<targets>` is one name or a comma-separated list of short names25 (`backend`, `frontend,contracts`). Run ListAgents and match each against the peer26 sessions' names (case-insensitive, substring). Exactly one match: use it. None, or27 several: ask with AskUserQuestion, listing the candidates. Never message this session28 itself.292. **Settle what is shared.** If the request needs something two repos must agree on (an30 ABI, events, an API schema, types, env names) and no file holds it yet, write it first to31 a file every session can read (`<repo>/docs/shared/<feature>.md`, or the path the user32 names), and point every request at it. With several targets, each gets only its own33 part plus the shared file.343. **Send.** One SendMessage per target, written so the session can act without asking:35 - the goal in one or two sentences, in the user's words where possible;36 - the shared file path (if any) and what in it is fixed;37 - bounds: its own repo only, what not to touch;38 - what to return, and "when done, report back to `<this session's name>` with39 SendMessage: what changed (commits), how it was checked, anything left open";40 - that push, deploy, migrations and other irreversible steps still need the user's yes41 in that session.42 Send to independent targets in one message so they start at once; a target that builds43 on another's output waits until that one reports.444. **Track.** Add one pending task per target: "relay: <short name> — <request in a few45 words>". When its report arrives, check it (commits exist, claimed checks ran), mark the46 task completed, and tell the user what came back. If it reports a question, ask the user47 with AskUserQuestion and send the answer back.48 If ListAgents shows no peer sessions, say so: the other repo needs its own Claude session49 open on this machine.