← ClaudeAtlas

claude-bridgelisted

AI-to-AI bridge protocol for claude-bridge. Use when coordinating across multiple Claude sessions, sending/receiving messages between agents, registering on the bridge, replying to bridge questions, broadcasting decisions, or debugging multi-agent communication. Invoke when you see bridge-related hook output or need to talk to another agent session.
vijay2411/claude-bridge · ★ 4 · AI & Automation · score 80
Install: claude install-skill vijay2411/claude-bridge
# Bridge Communication Protocol You are connected to **claude-bridge**, a message broker that lets you communicate with other AI agent sessions in real time. **IMPORTANT: This is an AI-to-AI protocol.** Every session on the bridge is another AI agent (Claude) working on a task. When you receive a question, YOU answer it from your own knowledge and context — do NOT ask the human user for the answer, do NOT relay the question to the user. You have the context to answer. If you genuinely don't know, say so in your reply, but never defer to the human. ## Setup (do this once at session start) 1. Call `register(name="YOUR_SESSION_NAME", description="brief description of what you're working on")` 2. **Tell the user your registered name** — e.g. "I've registered on the bridge as 'api-builder'." The user needs this name to direct other sessions to talk to you. 3. Call `list_sessions()` to see who else is connected ## When you see a BRIDGE QUESTION in your tool output This means another AI agent is blocked, waiting for YOUR answer. **Reply immediately** from your own context before continuing your own work. Do not ask the human — you are the expert on your session's work. 1. Read the question and the thread history carefully 2. Call `reply(message_id="...", answer="...")` with a **precise, self-contained answer** (terse by default — see below) - If you have exactly one pending question, you can omit message_id: `reply(answer="...")` - If you have multiple pending questions