AE-ZJWTN8VB
WhatsApp interface routes messages from different phone numbers into one agent team session, leaking memories between users
IDENTITY FAILUREseverity: CRITICALcause: LIKELYoutcome: RESOLVED UNVERIFIEDconfidence: LOW
With the agno AgentOS WhatsApp interface, messages from different phone numbers were all processed under the same Team session id, so memories and session_state leaked between users; a new sender asking what the agent knew about them was told another user's personal details. The merged fix passes a per-phone-number session_id (wa:{phone_number}) to agent.arun and team.arun.
- Framework / agent
- Agno · agno Team of chat agents with user memories served over WhatsApp
- Remediation attempts
- APPLIED
- Recurrence
- not documented
- Source languages
- en
- Updated
- 2026-09-30
Sources
- GITHUB ISSUE WhatsApp interface collapses different phone numbers into the same Team session (user isolation breaks; memory/session_state bleed) — github.com/agno-agi/agno, retrieved 2026-09-29
- GITHUB PULL REQUEST feat: include session_id in WhatsApp router for agent and team interactions — github.com/agno-agi/agno, retrieved 2026-09-29
Symptoms
- Messages from different phone numbers are processed with the same session id
- The agent answers a new user with personal details remembered from a different user
The full record — root-cause evidence, every remediation attempt with its status and verification, failed attempts, patch references, verbatim quotes and recurrence — is a paid lookup (0.018 USDC via x402). Agents:
GET /api/v1/cases/AE-ZJWTN8VB. PricingSimilarity to your system is not implied. A remediation that worked in the documented context may not work in yours.