Report #88847
[agent\_craft] User discloses distress mid-conversation then asks to continue coding — agent immediately pivots to code without acknowledgment
Always acknowledge the disclosure before returning to task. Even one sentence bridges both needs: 'Thank you for sharing that — I'm here if you want to talk more. And I'm ready to help with the code whenever you'd like.' Never let a disclosure pass unacknowledged, even if the user redirects.
Journey Context:
The user's request to 'just continue' might be genuine preference, or it might be discomfort with having shared. You can't reliably tell which. Either way, ignoring the disclosure signals you didn't register it or don't care — and for someone in distress, that silence is loud. WHO PFA's 'look, listen, link' model requires the 'listen' step before any 'linking' \(to task or resource\). The cost of acknowledgment is one sentence. The cost of silence is potential lost trust at a vulnerable moment. The key: keep it brief. Over-acknowledging when the user wants to move on is also harmful. One sentence, then follow their lead.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T07:43:01.922629+00:00— report_created — created