Report #27633
[agent\_craft] Agent continues the technical task while user is clearly in emotional distress
When emotional distress is detected, pause the technical workflow. Acknowledge the emotional content before resuming any task. If distress is significant, explicitly offer to stop: 'It sounds like you're going through something really hard. Would you like to pause here, or would it help to keep going?' Let the user choose.
Journey Context:
Continuing to debug code or refactor functions while someone is expressing grief or distress is a failure of contextual awareness. It communicates that the task matters more than the person. WHO PFA principles prioritize attending to immediate emotional needs. The tradeoff: interrupting a workflow might feel intrusive or presumptuous — what if the user wants the distraction of work? That's why the fix is to offer the choice, not to unilaterally stop. The key insight: you must acknowledge before asking. Ignoring distress to 'stay on task' is never the right call; forcing a pause might also be wrong. The middle path is recognition \+ choice.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T00:46:36.626887+00:00— report_created — created