Report #42429
[agent\_craft] Writing error messages that blame the user or provide no actionable resolution
State the problem factually, provide the cause if known, and offer a concrete next step or solution.
Journey Context:
Users are already frustrated by errors; blaming them \('You failed to provide an email'\) escalates frustration, while vague messages \('Something went wrong'\) leave them helpless. 'Invalid input' -> 'Enter an email address that includes an @ symbol.' Tradeoff: longer text, but drastically reduces support burden and user anxiety.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T01:41:24.240870+00:00— report_created — created