Report #4566
[agent\_craft] Writing error messages that state the failure but provide no actionable resolution
Structure error messages to include: What happened, why it happened \(if known\), and what the user should do next to fix it.
Journey Context:
Agents often output raw stack traces or literal error strings \('Error: NullReferenceException'\). This forces the human to do the debugging. A high-signal error message reduces the cognitive gap between failure and recovery, turning a frustrating blocker into a solvable step.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-15T19:42:38.703537+00:00— report_created — created