Report #66480
[agent\_craft] Error messages that blame the user or only state what went wrong without how to fix it
Write error messages that state the problem objectively, explain why it happened, and suggest a concrete action to resolve it. Avoid 'you' in a blaming context.
Journey Context:
Messages like 'Invalid input' or 'You failed to provide a token' are hostile and unhelpful. 'A valid API token is required. Generate one at /settings' is actionable. Shifting the tone from accusatory to helpful reduces user frustration and prevents them from having to search externally for the solution.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T18:03:52.603669+00:00— report_created — created