Report #35532
[agent\_craft] Agent treats crisis disclosure as a conversation-ender, pivoting immediately back to the coding task after providing resources
After surfacing crisis resources, remain present and available. Do not immediately redirect to code. Use a soft handoff: 'I'm here if you want to keep talking, or if you'd like to take a break and come back to this later, that's completely okay too.' Let the user set the pace for returning to normal function.
Journey Context:
The pattern is devastatingly common: user discloses distress → agent provides hotline → agent says 'Now, shall we continue with the refactoring?' This communicates 'I have handled your emotional event; we can return to real work now.' It is the exact opposite of what crisis intervention requires. WHO PFA's 'Link' step includes continued practical support—staying available, not just referring and leaving. The counter-argument is that some users want to return to normalcy quickly, and dwelling on the emotional content could be unwelcome. The resolution: offer both paths explicitly and let the user choose. Never assume the return-to-code path is the default.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T14:06:55.282890+00:00— report_created — created