Broadcast groups

Broadcast groups 문서는 OpenClaw 공식 문서(channels/broadcast-groups)를 한국어로 정리한 가이드입니다. Broadcast a WhatsApp message to multiple agents 명령·설정 키·코드 예시는 공식 문서를 그대로 보존하며, 해석과 절차 안내는 한국어로 제공합니다. 최종 동작은 설치된 CLI 버전과 공식 원문을 확인하세요.

핵심 요약

Broadcast a WhatsApp message to multiple agents

한국어 가이드 범위: channels/broadcast-groups 경로의 설정·명령·제약·예시를 학습용으로 재구성합니다.

문서 구성

공식 문서의 주요 섹션은 다음과 같습니다.

개요
구성
Basic setup
Processing strategy
Complete example
동작 방식
Message flow
Session isolation
Example: isolated sessions
Use cases
Best practices
Compatibility
Providers
라우팅
트러블슈팅
예제
API reference
Config schema
Fields
제한 사항
관련 문서

상세 내용

본문

Status: Experimental. Added in 2026.1.9. WhatsApp (web channel) only.

개요

Broadcast groups run multiple agents on the same inbound message. Each agent processes the message in its own isolated session and posts its own reply, so one WhatsApp number can host a team of specialized agents in a single group chat or DM.

구성

이 섹션의 세부 항목은 공식 문서 구성를 참고하세요.

Basic setup

Add a top-level broadcast section (next to bindings). Keys are WhatsApp peer ids, values are arrays of agent ids:

주요 항목:

group chats: group JID (e.g. 120363403215116621@g.us)
DMs: sender E.164 phone number (e.g. +15551234567)

{
  "broadcast": {
    "120363403215116621@g.us": ["alfred", "baerbel", "assistant3"]
  }
}

Processing strategy

broadcast.strategy sets how agents process the message:

Strategy	Behavior
`parallel` (default)	All agents process simultaneously; replies arrive in any order.
`sequential`	Agents process in array order; each waits for the previous to finish.

{
  "broadcast": {
    "strategy": "sequential",
    "120363403215116621@g.us": ["alfred", "baerbel"]
  }
}

Complete example

{
  "agents": {
    "list": [
      {
        "id": "code-reviewer",
        "name": "Code Reviewer",
        "workspace": "/path/to/code-reviewer",
        "sandbox": { "mode": "all" }
      },
      {
        "id": "security-auditor",
        "name": "Security Auditor",
        "workspace": "/path/to/security-auditor",
        "sandbox": { "mode": "all" }
      },
      {
        "id": "docs-generator",
        "name": "Documentation Generator",
        "workspace": "/path/to/docs-generator",
        "sandbox": { "mode": "all" }
      }
    ]
  },
  "broadcast": {
    "strategy": "parallel",
    "120363403215116621@g.us": ["code-reviewer", "security-auditor", "docs-generator"],
    "120363424282127706@g.us": ["support-en", "support-de"],
    "+15555550123": ["assistant", "logger"]
  }
}

동작 방식

이 섹션의 세부 항목은 공식 문서 동작 방식를 참고하세요.

Message flow

OpenClaw applies channel allowlists, group activation rules, and configured ACP binding ownership.

주요 항목:

All listed agents process the message.
Each agent has its own session key and isolated context.
Agents process in parallel (default) or sequentially.
Audio attachments are transcribed once before fan-out, so agents share one transcript instead of making separate STT calls.

Session isolation

Each agent in a broadcast group maintains completely separate:

주요 항목:

Session keys (agent:alfred:whatsapp:group:120363... vs agent:baerbel:whatsapp:group:120363...)
Conversation history (an agent does not see other agents' replies)
Workspace (separate sandboxes if configured)
Tool access (different allow/deny lists)
Memory/context (separate IDENTITY.md, SOUL.md, etc.)

Example: isolated sessions

In group 120363403215116621@g.us with agents ["alfred", "baerbel"]:

Session: agent:alfred:whatsapp:group:120363403215116621@g.us
    History: [user message, alfred's previous responses]
    Workspace: ~/openclaw-alfred/
    Tools: read, write, exec

Session: agent:baerbel:whatsapp:group:120363403215116621@g.us
    History: [user message, baerbel's previous responses]
    Workspace: ~/openclaw-baerbel/
    Tools: read only

Use cases

주요 항목:

Specialized agent teams: a dev group where code-reviewer, security-auditor, test-generator, and docs-checker each answer the same message from their own angle.
Multi-language support: one support chat with support-en, support-de, support-es responding in their languages.
Quality assurance: support-agent answers while qa-agent reviews and only responds when it finds issues.
Task automation: task-tracker, time-logger, and report-generator all consume the same status update.

Best practices

Give each agent a single, clear responsibility (formatter, linter, tester) instead of one generic "dev-helper" agent.

{
      "agents": {
        "list": [
          { "id": "security-scanner", "name": "Security Scanner" },
          { "id": "code-formatter", "name": "Code Formatter" },
          { "id": "test-generator", "name": "Test Generator" }
        ]
      }
    }

{
      "agents": {
        "list": [
          { "id": "reviewer", "tools": { "allow": ["read", "exec"] } },
          { "id": "fixer", "tools": { "allow": ["read", "write", "edit", "exec"] } }
        ]
      }
    }

Compatibility

이 섹션의 세부 항목은 공식 문서 Compatibility를 참고하세요.

Providers

Broadcast groups are currently implemented for WhatsApp (web channel) only. Other channels ignore the broadcast config.

라우팅

Broadcast groups work alongside existing routing:

주요 항목:

GROUP_A: only alfred responds (normal routing).
GROUP_B: agent1 AND agent2 respond (broadcast).

{
  "bindings": [
    {
      "match": { "channel": "whatsapp", "peer": { "kind": "group", "id": "GROUP_A" } },
      "agentId": "alfred"
    }
  ],
  "broadcast": {
    "GROUP_B": ["agent1", "agent2"]
  }
}

트러블슈팅

Agent IDs exist in agents.entries (config validation rejects unknown ids). 2. Peer ID format is correct (group JID like 120363403215116621@g.us, or E.164 like +15551234567 for DMs). 3. The message passed normal gating (mention/activation rules still apply).

openclaw logs --follow | grep -i broadcast

예제

One code snippet in the group produces four replies: formatting fixes, a security finding, a coverage gap, and a docs nit.

{
      "broadcast": {
        "strategy": "parallel",
        "120363403215116621@g.us": [
          "code-formatter",
          "security-scanner",
          "test-coverage",
          "docs-checker"
        ]
      },
      "agents": {
        "list": [
          {
            "id": "code-formatter",
            "workspace": "~/agents/formatter",
            "tools": { "allow": ["read", "write"] }
          },
          {
            "id": "security-scanner",
            "workspace": "~/agents/security",
            "tools": { "allow": ["read", "exec"] }
          },
          {
            "id": "test-coverage",
            "workspace": "~/agents/testing",
            "tools": { "allow": ["read", "exec"] }
          },
          { "id": "docs-checker", "workspace": "~/agents/docs", "tools": { "allow": ["read"] } }
        ]
      }
    }

{
      "broadcast": {
        "strategy": "sequential",
        "+15555550123": ["detect-language", "translator-en", "translator-de"]
      },
      "agents": {
        "list": [
          { "id": "detect-language", "workspace": "~/agents/lang-detect" },
          { "id": "translator-en", "workspace": "~/agents/translate-en" },
          { "id": "translator-de", "workspace": "~/agents/translate-de" }
        ]
      }
    }

API reference

이 섹션의 세부 항목은 공식 문서 API reference를 참고하세요.

Config schema

interface OpenClawConfig {
  broadcast?: {
    strategy?: "parallel" | "sequential";
    [peerId: string]: string[];
  };
}

Fields

How to process agents. parallel runs all agents simultaneously; sequential runs them in array order.

제한 사항

Max agents: no hard limit, but many agents (10+) can be slow. 2. Shared context: agents do not see each other's responses (by design). 3. Message ordering: parallel responses may arrive in any order. 4. Rate limits: all replies come from one WhatsApp account, so every agent's reply counts toward the same WhatsApp rate limits.

실습 체크리스트

공식 문서와 로컬 버전을 대조합니다: https://docs.openclaw.ai/channels/broadcast-groups
관련 CLI는 openclaw --help 및 하위 명령 --help로 옵션을 확인합니다.
설정 변경 시 openclaw config / openclaw doctor로 유효성을 검사합니다.
Gateway·채널·플러그인 변경 후에는 필요 시 Gateway를 재시작합니다.

자주 쓰는 명령·설정 예시

{
  "broadcast": {
    "120363403215116621@g.us": ["alfred", "baerbel", "assistant3"]
  }
}

{
  "broadcast": {
    "strategy": "sequential",
    "120363403215116621@g.us": ["alfred", "baerbel"]
  }
}

{
  "agents": {
    "list": [
      {
        "id": "code-reviewer",
        "name": "Code Reviewer",
        "workspace": "/path/to/code-reviewer",
        "sandbox": { "mode": "all" }
      },
      {
        "id": "security-auditor",
        "name": "Security Auditor",
        "workspace": "/path/to/security-auditor",
        "sandbox": { "mode": "all" }
      },
      {
        "id": "docs-generator",
        "name": "Documentation Generator",
        "workspace": "/path/to/docs-generator",
        "sandbox": { "mode": "all" }
      }
    ]
  },
  "broadcast": {
    "strategy": "parallel",
    "120363403215116621@g.us": ["code-reviewer", "security-auditor", "docs-generator"],
    "120363424282127706@g.us": ["support-en", "support-de"],
    "+15555550123": ["assistant", "logger"]
  }
}

Session: agent:alfred:whatsapp:group:120363403215116621@g.us
    History: [user message, alfred's previous responses]
    Workspace: ~/openclaw-alfred/
    Tools: read, write, exec

Session: agent:baerbel:whatsapp:group:120363403215116621@g.us
    History: [user message, baerbel's previous responses]
    Workspace: ~/openclaw-baerbel/
    Tools: read only

{
      "agents": {
        "list": [
          { "id": "security-scanner", "name": "Security Scanner" },
          { "id": "code-formatter", "name": "Code Formatter" },
          { "id": "test-generator", "name": "Test Generator" }
        ]
      }
    }

Broadcast groups

핵심 요약

Broadcast a WhatsApp message to multiple agents

한국어 가이드 범위: channels/broadcast-groups 경로의 설정·명령·제약·예시를 학습용으로 재구성합니다.

문서 구성

공식 문서의 주요 섹션은 다음과 같습니다.

개요
구성
Basic setup
Processing strategy
Complete example
동작 방식
Message flow
Session isolation
Example: isolated sessions
Use cases
Best practices
Compatibility
Providers
라우팅
트러블슈팅
예제
API reference
Config schema
Fields
제한 사항
관련 문서

상세 내용

본문

Status: Experimental. Added in 2026.1.9. WhatsApp (web channel) only.

개요

구성

이 섹션의 세부 항목은 공식 문서 구성를 참고하세요.

Basic setup

Add a top-level broadcast section (next to bindings). Keys are WhatsApp peer ids, values are arrays of agent ids:

주요 항목:

group chats: group JID (e.g. 120363403215116621@g.us)
DMs: sender E.164 phone number (e.g. +15551234567)

{
  "broadcast": {
    "120363403215116621@g.us": ["alfred", "baerbel", "assistant3"]
  }
}

Processing strategy

broadcast.strategy sets how agents process the message:

Strategy	Behavior
`parallel` (default)	All agents process simultaneously; replies arrive in any order.
`sequential`	Agents process in array order; each waits for the previous to finish.

{
  "broadcast": {
    "strategy": "sequential",
    "120363403215116621@g.us": ["alfred", "baerbel"]
  }
}

Complete example

{
  "agents": {
    "list": [
      {
        "id": "code-reviewer",
        "name": "Code Reviewer",
        "workspace": "/path/to/code-reviewer",
        "sandbox": { "mode": "all" }
      },
      {
        "id": "security-auditor",
        "name": "Security Auditor",
        "workspace": "/path/to/security-auditor",
        "sandbox": { "mode": "all" }
      },
      {
        "id": "docs-generator",
        "name": "Documentation Generator",
        "workspace": "/path/to/docs-generator",
        "sandbox": { "mode": "all" }
      }
    ]
  },
  "broadcast": {
    "strategy": "parallel",
    "120363403215116621@g.us": ["code-reviewer", "security-auditor", "docs-generator"],
    "120363424282127706@g.us": ["support-en", "support-de"],
    "+15555550123": ["assistant", "logger"]
  }
}

동작 방식

이 섹션의 세부 항목은 공식 문서 동작 방식를 참고하세요.

Message flow

OpenClaw applies channel allowlists, group activation rules, and configured ACP binding ownership.

주요 항목:

All listed agents process the message.
Each agent has its own session key and isolated context.
Agents process in parallel (default) or sequentially.
Audio attachments are transcribed once before fan-out, so agents share one transcript instead of making separate STT calls.

Session isolation

Each agent in a broadcast group maintains completely separate:

주요 항목:

Session keys (agent:alfred:whatsapp:group:120363... vs agent:baerbel:whatsapp:group:120363...)
Conversation history (an agent does not see other agents' replies)
Workspace (separate sandboxes if configured)
Tool access (different allow/deny lists)
Memory/context (separate IDENTITY.md, SOUL.md, etc.)

Example: isolated sessions

In group 120363403215116621@g.us with agents ["alfred", "baerbel"]:

Session: agent:alfred:whatsapp:group:120363403215116621@g.us
    History: [user message, alfred's previous responses]
    Workspace: ~/openclaw-alfred/
    Tools: read, write, exec

Session: agent:baerbel:whatsapp:group:120363403215116621@g.us
    History: [user message, baerbel's previous responses]
    Workspace: ~/openclaw-baerbel/
    Tools: read only

Use cases

주요 항목:

Specialized agent teams: a dev group where code-reviewer, security-auditor, test-generator, and docs-checker each answer the same message from their own angle.
Multi-language support: one support chat with support-en, support-de, support-es responding in their languages.
Quality assurance: support-agent answers while qa-agent reviews and only responds when it finds issues.
Task automation: task-tracker, time-logger, and report-generator all consume the same status update.

Best practices

Give each agent a single, clear responsibility (formatter, linter, tester) instead of one generic "dev-helper" agent.

{
      "agents": {
        "list": [
          { "id": "security-scanner", "name": "Security Scanner" },
          { "id": "code-formatter", "name": "Code Formatter" },
          { "id": "test-generator", "name": "Test Generator" }
        ]
      }
    }

{
      "agents": {
        "list": [
          { "id": "reviewer", "tools": { "allow": ["read", "exec"] } },
          { "id": "fixer", "tools": { "allow": ["read", "write", "edit", "exec"] } }
        ]
      }
    }

Compatibility

이 섹션의 세부 항목은 공식 문서 Compatibility를 참고하세요.

Providers

Broadcast groups are currently implemented for WhatsApp (web channel) only. Other channels ignore the broadcast config.

라우팅

Broadcast groups work alongside existing routing:

주요 항목:

GROUP_A: only alfred responds (normal routing).
GROUP_B: agent1 AND agent2 respond (broadcast).

{
  "bindings": [
    {
      "match": { "channel": "whatsapp", "peer": { "kind": "group", "id": "GROUP_A" } },
      "agentId": "alfred"
    }
  ],
  "broadcast": {
    "GROUP_B": ["agent1", "agent2"]
  }
}

트러블슈팅

Agent IDs exist in agents.entries (config validation rejects unknown ids). 2. Peer ID format is correct (group JID like 120363403215116621@g.us, or E.164 like +15551234567 for DMs). 3. The message passed normal gating (mention/activation rules still apply).

openclaw logs --follow | grep -i broadcast

예제

One code snippet in the group produces four replies: formatting fixes, a security finding, a coverage gap, and a docs nit.

{
      "broadcast": {
        "strategy": "parallel",
        "120363403215116621@g.us": [
          "code-formatter",
          "security-scanner",
          "test-coverage",
          "docs-checker"
        ]
      },
      "agents": {
        "list": [
          {
            "id": "code-formatter",
            "workspace": "~/agents/formatter",
            "tools": { "allow": ["read", "write"] }
          },
          {
            "id": "security-scanner",
            "workspace": "~/agents/security",
            "tools": { "allow": ["read", "exec"] }
          },
          {
            "id": "test-coverage",
            "workspace": "~/agents/testing",
            "tools": { "allow": ["read", "exec"] }
          },
          { "id": "docs-checker", "workspace": "~/agents/docs", "tools": { "allow": ["read"] } }
        ]
      }
    }

{
      "broadcast": {
        "strategy": "sequential",
        "+15555550123": ["detect-language", "translator-en", "translator-de"]
      },
      "agents": {
        "list": [
          { "id": "detect-language", "workspace": "~/agents/lang-detect" },
          { "id": "translator-en", "workspace": "~/agents/translate-en" },
          { "id": "translator-de", "workspace": "~/agents/translate-de" }
        ]
      }
    }

API reference

이 섹션의 세부 항목은 공식 문서 API reference를 참고하세요.

Config schema

interface OpenClawConfig {
  broadcast?: {
    strategy?: "parallel" | "sequential";
    [peerId: string]: string[];
  };
}

Fields

How to process agents. parallel runs all agents simultaneously; sequential runs them in array order.

제한 사항

Max agents: no hard limit, but many agents (10+) can be slow. 2. Shared context: agents do not see each other's responses (by design). 3. Message ordering: parallel responses may arrive in any order. 4. Rate limits: all replies come from one WhatsApp account, so every agent's reply counts toward the same WhatsApp rate limits.

실습 체크리스트

공식 문서와 로컬 버전을 대조합니다: https://docs.openclaw.ai/channels/broadcast-groups
관련 CLI는 openclaw --help 및 하위 명령 --help로 옵션을 확인합니다.
설정 변경 시 openclaw config / openclaw doctor로 유효성을 검사합니다.
Gateway·채널·플러그인 변경 후에는 필요 시 Gateway를 재시작합니다.

자주 쓰는 명령·설정 예시

{
  "broadcast": {
    "120363403215116621@g.us": ["alfred", "baerbel", "assistant3"]
  }
}

{
  "broadcast": {
    "strategy": "sequential",
    "120363403215116621@g.us": ["alfred", "baerbel"]
  }
}

{
  "agents": {
    "list": [
      {
        "id": "code-reviewer",
        "name": "Code Reviewer",
        "workspace": "/path/to/code-reviewer",
        "sandbox": { "mode": "all" }
      },
      {
        "id": "security-auditor",
        "name": "Security Auditor",
        "workspace": "/path/to/security-auditor",
        "sandbox": { "mode": "all" }
      },
      {
        "id": "docs-generator",
        "name": "Documentation Generator",
        "workspace": "/path/to/docs-generator",
        "sandbox": { "mode": "all" }
      }
    ]
  },
  "broadcast": {
    "strategy": "parallel",
    "120363403215116621@g.us": ["code-reviewer", "security-auditor", "docs-generator"],
    "120363424282127706@g.us": ["support-en", "support-de"],
    "+15555550123": ["assistant", "logger"]
  }
}

Session: agent:alfred:whatsapp:group:120363403215116621@g.us
    History: [user message, alfred's previous responses]
    Workspace: ~/openclaw-alfred/
    Tools: read, write, exec

Session: agent:baerbel:whatsapp:group:120363403215116621@g.us
    History: [user message, baerbel's previous responses]
    Workspace: ~/openclaw-baerbel/
    Tools: read only

{
      "agents": {
        "list": [
          { "id": "security-scanner", "name": "Security Scanner" },
          { "id": "code-formatter", "name": "Code Formatter" },
          { "id": "test-generator", "name": "Test Generator" }
        ]
      }
    }

Broadcast groups

핵심 요약

문서 구성

상세 내용

본문

개요

구성

Basic setup

Processing strategy

Complete example

동작 방식

Message flow

Session isolation

Example: isolated sessions

Use cases

Best practices

Compatibility

Providers

라우팅

트러블슈팅

예제

API reference

Config schema

Fields

제한 사항

관련 문서

실습 체크리스트

자주 쓰는 명령·설정 예시

관련 링크

관련 가이드

Broadcast groups

핵심 요약

문서 구성

상세 내용

본문

개요

구성

Basic setup

Processing strategy

Complete example

동작 방식

Message flow

Session isolation

Example: isolated sessions

Use cases

Best practices

Compatibility

Providers

라우팅

트러블슈팅

예제

API reference

Config schema

Fields

제한 사항

관련 문서

실습 체크리스트

자주 쓰는 명령·설정 예시

관련 링크

관련 가이드