← 返回
沟通协作 中文

Multi-Agent Chat Protocol

Prevent common failures in multi-agent Discord conversations. Use when multiple AI agents (bots) are chatting in the same channel — townhalls, group discussi...
防止多智能体Discord对话中的常见故障。适用于多个AI代理(机器人)在同一频道中进行交流的场景——如全体会议、群组讨论等。
mupengi-bot
沟通协作 clawhub v1.0.0 1 版本 100000 Key: 无需
★ 0
Stars
📥 801
下载
💾 6
安装
1
版本
#latest

概述

Multi-Agent Chat Protocol

Rules for AI agents participating in multi-bot Discord conversations. Follow strictly to prevent token waste, context overflow, and communication failures.

Core Rules

1. Turn-Based Communication

  • One agent answers at a time — wait for your turn
  • Mention one agent per message when directing questions
  • Never answer a question directed at another agent

2. One Response Per Topic

  • One answer per agenda item — never repeat yourself
  • If someone missed your answer: reply "위에 있어" (one line only)
  • Never re-explain what you already said

3. No Bot-to-Bot Reactions

  • Never add emoji reactions to bot messages — each reaction event consumes hundreds of tokens
  • Reactions are for humans only
  • Set reactionNotifications: "off" in config to stop receiving reaction events

4. Short Responses

  • Keep answers under 200 words unless explicitly asked for detail
  • No filler ("네 알겠습니다!", "감사합니다!" alone) — use NO_REPLY instead
  • If you have nothing to add: NO_REPLY

5. Follow the Agenda

  • When a new topic is announced, stop discussing the previous one
  • Don't circle back to resolved topics
  • If asked a question, answer that specific question — not a previous one

6. Loop Prevention

  • Max 4 consecutive bot-to-bot exchanges before requiring human input
  • If the same question is asked 3+ times, stop and flag to the human operator
  • Never create ping-pong chains between bots

Config Optimization

Each bot should set in config.yml:

channels:
  discord:
    reactionNotifications: "off"

Token Budget Guidelines

  • Multi-agent channels: use Sonnet or cheaper models (not Opus)
  • Separate API keys per bot to avoid shared rate limits
  • Estimate: 3+ bots on Opus = ~1000 KRW per round of conversation

Red Flags (Stop & Alert Human)

  • Same question repeated 3+ times → context window issue, alert operator
  • Rate limit errors appearing → need API key separation
  • Bot responding to wrong agenda item → confusion, pause and clarify
  • Token usage spiking → check for reaction events or verbose responses

Lessons Learned

These rules come from a real 2026-03-07 townhall incident:

  • 3 bots simultaneously responding caused context overflow
  • Lead agent repeated same question 6+ times (couldn't see answers in context)
  • Emoji reactions (👀🤔👨‍💻👍 cycles) consumed massive tokens silently
  • Shared API key caused rate limits for all bots simultaneously
  • Cost: ~1000 KRW per exchange on Opus model

版本历史

共 1 个版本

  • v1.0.0 当前
    2026-03-30 16:29 安全 安全

安全检测

腾讯云安全 (Keen)

安全,无风险
查看报告

腾讯云安全 (Sanbu)

安全,无风险
查看报告

🔗 相关推荐

communication-collaboration

Slack

steipete
当需要通过 slack 工具从 Clawdbot 控制 Slack 时使用,包括在频道或私信中回复消息或置顶/取消置顶项目。
★ 157 📥 47,685
communication-collaboration

Himalaya

lamelas
{"answer":"通过IMAP/SMTP管理邮件的CLI。可在终端使用 `himalaya` 收发、回复、转发、搜索及整理邮件。支持多账户与MML(MIME元语言)编写邮件。"}
★ 68 📥 45,592
communication-collaboration

imap-smtp-email

gzlicanyi
使用IMAP/SMTP读取和发送邮件;检查新/未读邮件、获取内容、搜索邮箱、标记已读/未读、发送带附件的邮件。支持...
★ 114 📥 52,432