WhatsApp Adds Third-Party AI Agent Chats: Up to Five per Account

WhatsApp is finally treating AI agents as first-class chat partners. WABetaInfo spotted the feature in Android beta builds, and 9to5Mac’s September 7, 2026 write-up confirms users can connect up to five third-party agents via API keys—with a privacy trade-off that matters.

How the setup works

In supported builds (WABetaInfo cites WhatsApp beta for Android 2.26.35.3), Settings gains an Agents entry. You name the agent, pick a profile photo, and WhatsApp generates an API key that you paste into the external agent platform (OpenAI, Anthropic, Google stacks, or simpler bots). Once linked, the agent appears as its own conversation in the chat list.

Scope is intentionally narrow. The agent can only read what you send in that dedicated thread—not your other chats, contacts, or media. You cannot drop agents into groups or communities yet. WhatsApp also warns that AI replies may be inaccurate, so treat outputs like any other LLM draft.

The encryption caveat

WABetaInfo is blunt: chats with agents are not end-to-end encrypted. Messages travel through a Meta service on behalf of the agent developer, so the developer can access that content as part of the service. Ordinary person-to-person WhatsApp messages and calls remain E2EE. If you were hoping for a fully sealed agent sidecar, this is not it.

Rollout status

Availability is limited to select Android users in some countries, with a broader expansion “over the coming months” and no firm global date. iOS timing is not detailed in these reports. For Rocks apps readers, the practical move is to wait for the Agents section to appear, start with a low-sensitivity agent (calendar helper, not banking), and assume anything typed into an agent chat is visible to that agent’s operator.

Why Meta is doing this now

9to5Mac’s context is useful: unofficial WhatsApp bots used to risk account bans, while Telegram leaned into agent workflows. Native agent chats are Meta’s way to keep those automations inside WhatsApp without the brittle workarounds. WABetaInfo stresses you can reset an API key anytime, and removing an agent disconnects replies without wiping the visible history—handy if you rotate tools.

Still, five agents per account is a power-user ceiling, not a team workspace. Until group support exists, treat this as a personal command channel. Pair it with Muse or other Meta AI products only after you understand which threads are E2EE and which are not—the distinction is easy to miss when everything still “looks like WhatsApp.”

Why Meta is doing this now

9to5Mac’s context is useful: unofficial WhatsApp bots used to risk account bans, while Telegram leaned into agent workflows. Native agent chats are Meta’s way to keep those automations inside WhatsApp without the brittle workarounds. WABetaInfo stresses you can reset an API key anytime, and removing an agent disconnects replies without wiping the visible history—handy if you rotate tools.

Still, five agents per account is a power-user ceiling, not a team workspace. Until group support exists, treat this as a personal command channel. Pair it with Muse or other Meta AI products only after you understand which threads are E2EE and which are not—the distinction is easy to miss when everything still “looks like WhatsApp.”

Sources: 9to5Mac, WABetaInfo.