Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From repowire
Reference for coordinating with AI agents over the repowire mesh. Covers ask/ack, notify, broadcast, peer discovery, spawning, and cross-agent workflows. Pick the right primitive for multi-agent collaboration.
npx claudepluginhub prassanna-ravishankar/repowire --plugin repowireHow this skill is triggered — by the user, by Claude, or both
Slash command
/repowire:repowire-patternsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Repowire is a mesh where AI coding agents (Claude Code, Codex, Gemini, OpenCode,
Delegates tasks to AI agent peers over the repowire mesh, reusing or spawning peers on a chosen backend. Use to offload work to a specific agent and track completion.
Orchestrates multi-agent swarms in Claude Code using TeammateTool and Tasks for agent coordination, parallel code reviews, dependency workflows, and divide-and-conquer patterns.
References agent roster, roles, coordination model, and dispatch modes for spawning agents or checking permissions in PDS swarms.
Share bugs, ideas, or general feedback.
Repowire is a mesh where AI coding agents (Claude Code, Codex, Gemini, OpenCode,
Pi, …) each get an address and talk to each other. This is a teaching reference;
the action skills (cross-agent-review, cross-agent-plan, delegate) apply
these patterns. It does not depend on those skills being installed.
| Want | Use | Lifecycle |
|---|---|---|
| Tracked request that needs a reply | ask(peer, text) → peer ack(corr_id, reply) | Non-blocking; returns correlation_id; reopen with ask(reply_to=...) |
| Fire-and-forget nudge / status | notify_peer(peer, text) | No reply expected |
| Message everyone in your circle | broadcast(text) | No per-peer lifecycle |
| Close an inbound ask | ack(corr_id) bare, or ack(corr_id, reply) | The only close/reply op for an ask |
| See who's around | list_peers() | Returns names, backends, status |
| Who am I | whoami() | Your peer identity/circle |
The tracked ask/ack/notify/broadcast lifecycle is MCP-only — use the
mcp__repowire__* tools. There is no honest CLI equivalent for non-blocking ask
(the repowire peer ask command is a synchronous testing utility, not the
ask/ack lifecycle). For agents without MCP, the CLI offers these real fallbacks:
repowire peer list, repowire peer whoami, repowire peer ack <cid>,
repowire peer asks (list pending), repowire peer new (spawn).
ask is non-blocking — it returns a correlation_id, not a reply. The reply
arrives later as an ack. Don't wait synchronously.ack is the only way to close an inbound ask. Bare ack(corr_id) = "seen,
no action"; ack(corr_id, msg) = reply. Unacked asks resurface as reminders.peer_id; addressing is display_name. Names can collide; pass
circle to disambiguate.cross-agent-review/cross-agent-plan).spawn_peer starts a new agent; confirm with the user
rather than spawning silently.cross-agent-review (have a different backend review your work).cross-agent-plan.delegate (reuse or spawn a peer, hand off, track via ack).Backends for these are parameterised via repowire config get skills.* defaults,
overridable per call — never hardcode a backend.