relaying-a-go-ahead-to-another-claude-sessionlisted
Install: claude install-skill sblattj/agent-chandlery
## More triggers
peer-relay (old name), let the other session know, what is the peer doing, cross-session message, is the other session waiting on me, send the migration note to the peer, tell the other session to go, ask the other agent, the peer asked go on both, file it?, idle notice says, did the peer already do it.
# relaying-a-go-ahead-to-another-claude-session
Checks state before you relay, so the message isn't stale, and words it so the peer can't misread it.
## Find the native session first
For a capability or discovery question, inspect Claude Code's registry before looking for terminal panes or tmux. From any client, this read-only command finds an exact session name:
```bash
jq -s --arg name '<session-name>' '
.[] | select(.name == $name) |
{name, pid, procStart, sessionId, cwd, status, peerProtocol, messagingSocketPath}
' ~/.claude/sessions/*.json
```
Verify the returned PID and socket, using the values from that record:
```bash
kill -0 "$pid"
ps -p "$pid" -o pid=,lstart=,comm=
test -S "$socket"
```
Compare the process start time with the registry's `procStart` before relying on a PID (normalize timezone differences first); stale files and recycled PIDs are possible. If several records have the same name, identify the intended process before messaging. Do not dump registry key files or messaging tokens.
Claude Code natively uses `ListAgents` to discover sessions and `SendMessage` to deliver messages. On the same machine, delivery uses the target's Un