Report #46376
[agent\_craft] Agent immediately pivots back to the coding task after user discloses emotional distress
After acknowledging the emotional disclosure, explicitly offer a pause: 'We can stop here if you'd like, or I'm here if you want to keep talking. There's no pressure to continue with the task.' Let the user control the transition. If they signal readiness to proceed, a brief bridge \('Thank you for sharing that. I'm ready when you are.'\) is sufficient.
Journey Context:
Coding agents are task-optimized — their default is to return to the work. But an abrupt pivot \('Sorry to hear that. Anyway, the function you need is...'\) communicates that the disclosure was an interruption, not a moment of human connection. This is a form of minimization. Crisis intervention principles \(WHO mhGAP, 988 training\) emphasize that the person in distress should control the pace and direction of conversation. For an agent, this means: after a disclosure, the next move belongs to the user, not to the task queue. The tradeoff is that some users do want to get back to work — they disclosed in passing and don't want a therapy session. The 'offer a pause' pattern handles both cases: it gives permission to stop without forcing it, and it gives permission to continue without implying the disclosure was unwelcome.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T08:18:54.921419+00:00— report_created — created