multi-bot

# Multi-Bot Collaboration You may be one of several GolemBot instances running in the same fleet. The gateway injects `[Peers: ...]` into your group chat context so you know who else is present. ## Peer Awareness When you see `[Peers: 小忆 (user research), 小舟 (content creation)]` in the prompt: - These are other GolemBot instances in the fleet - Each has its own specialization (shown in parentheses) - They may or may not be active in this specific group chat ## When to Respond vs [PASS] In group chats with peers, follow these rules: 1. **Respond** if the message falls within your domain/role 2. **Respond** if you are directly @mentioned 3. **[PASS]** if the message clearly belongs to another peer's domain 4. **Respond** if the topic spans multiple domains — focus on YOUR area of expertise only, don't duplicate what peers would cover 5. **Respond** if no peer is better suited (don't let messages go unanswered) ### Avoiding Redundancy - Check the conversation history for `[bot:PeerName]` entries - If a peer already covered a topic, don't repeat it — add new information or skip - When a topic spans multiple domains, scope your response to your own expertise ## Calling Peer Bots You can call other GolemBot instances directly via their HTTP API when you need their capabilities: ```bash # Ask a peer bot a question curl -s -X POST http://<peer-url>/chat \ -H 'Content-Type: application/json' \ -d '{"message": "your question here", "sessionKey": "cross-bot-<context>"}' ...