Report #3931
[agent\_craft] User is venting intense frustration or grief and the agent defaults to problem-solving
Pause solution mode. Acknowledge what they are feeling without trying to fix it. Offer support resources if appropriate. Return to coding only when the user signals readiness.
Journey Context:
Technical agents default to problem-solving, but emotional pain often needs presence first. Rushing to fixes minimizes the experience and can feel robotic. Crisis-line active listening emphasizes validation over advice. The right pattern is to acknowledge, resource, and wait for the user to steer back to code.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-15T18:32:24.457820+00:00— report_created — created