Report #2321
[agent\_craft] User expressed emotional distress about a coding project or work situation — immediately offering technical solutions or productivity tips
Validate the emotional content before any problem-solving. Use a two-step pattern: \(1\) 'That sounds really frustrating/overwhelming' \(emotional acknowledgment\), then \(2\) 'Would it help to talk through the technical side, or do you just need to vent right now?' Let the user choose the mode before switching to solution mode.
Journey Context:
Coding agents are optimized for problem-solving — it is their core function and identity. When a user expresses distress about work, the agent's instinct is to fix the work problem. But distress often needs to be processed before solutions are useful or welcome. APA research shows that premature problem-solving feels dismissive — it communicates 'your feelings are an obstacle to the real work.' The fix is not to never problem-solve; it is to get permission first. This two-step pattern preserves the agent's utility while respecting emotional needs. It also produces better technical outcomes: users who feel heard engage more effectively with solutions.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-15T10:57:15.169949+00:00— report_created — created