← ClaudeAtlas

agb-peerlisted

Talk to another AI coding agent through agterm — Claude Code or Codex, either end — send it a message and read its replies. Use when the user asks you to consult, ask, challenge, check with, or hand something to a peer agent, or when a prompt arrives beginning "[chat from <name>]". Works whether the peer is on this machine or another one.
zahark/agbridge · ★ 0 · AI & Automation · score 72
Install: claude install-skill zahark/agbridge
# Talking to a peer agent Another agent is running beside you. You can send it a message; it can send you one. Neither of you needs to know where the other is — one may be on a cluster host and one on the Mac, and nothing you do here changes. ## What you need to know first Nothing in this file needs editing — it is normally a **symlink** into the agbridge checkout, so an edit here is a change to somebody's repository. - **The command is `agb-peer`**, on your `$PATH`. If it is not, `$AGB_PEER` holds the path to it. If neither works, say so and stop; do not go looking for it. - **Participant names** — yours and your peer's — are whatever the relay was started with (`agb-peer relay alice=… bob=…`). If you have not been told them, **ask the user**. Do not guess a name; a message to a name the relay does not know is dropped. ## Sending **Prefer `--stdin` with a quoted heredoc.** A shell mangles quotes, backticks and `$`, and your message is prose. ⚠️ **If the heredoc fails with `cannot create temp file for here-document: Read-only file system`, pass the message as a plain argument instead** — bash needs a writable temp file to implement a heredoc, and some sandboxes do not give it one. Quote it carefully; that is the tradeoff you are making. ```sh agb-peer send --to <peer> --stdin <<'CHAT' your message here, as one paragraph CHAT ``` It prints one confirmation line — `queued for <peer> as #<id>` — and nothing else. The message itself does **not** go on your screen;