# Broadcast Groups Documentation

## Overview

Broadcast Groups allow multiple agents to simultaneously process identical messages within a single WhatsApp conversation using one phone number. This experimental feature (added in version 2026.1.9) enables specialized agent teams to collaborate by each providing their unique perspective on user input.

## Key Capabilities

The feature supports four primary use cases:

1. **Specialized Agent Teams** – Agents with focused responsibilities (e.g., code reviewer, security auditor, documentation bot) all analyze the same message
2. **Multi-Language Support** – Different agents respond in their respective languages
3. **Quality Assurance** – Specialized agents validate outputs from primary agents
4. **Task Automation** – Multiple agents handle different aspects of a workflow simultaneously

## Configuration Structure

Broadcast groups are defined via a top-level `broadcast` section in configuration files, keyed by WhatsApp peer IDs:

- Group chats use the group JID format (e.g., `120363403215116621@g.us`)
- Direct messages use E.164 phone numbers (e.g., `+15551234567`)

Each peer ID maps to an array of agent identifiers that should process incoming messages.

## Processing Strategies

Two processing modes are available:

- **Parallel (default):** All agents process messages simultaneously for speed
- **Sequential:** Agents process in array order, with each waiting for the previous to complete

## Session Isolation

Each agent maintains completely independent:

- Session keys and conversation history
- Workspace and sandbox environment
- Tool access permissions
- Memory and personality context (IDENTITY.md, SOUL.md)

Agents process the message while maintaining completely separate session keys and isolated context.

## Important Notes

- Broadcast activation respects existing channel allowlists and group activation rules
- Broadcast takes priority over standard bindings configuration
- Currently limited to WhatsApp; Telegram, Discord, and Slack support are planned
- One agent's failure doesn't block other agents from responding