Report #40691
[gotcha] AI refusals create a UX dead end with no path forward
When a refusal is detected, intercept it and provide actionable UI alternatives \(e.g., 'I can't do X, but I can do Y or Z'\), or offer a one-click prompt rephrasing button.
Journey Context:
When an AI refuses \(due to safety filters or capability limits\), it outputs a canned 'I cannot assist with that.' The UI just displays this as the final word. The user is stuck and frustrated. The UI should parse refusals and offer a pivot. Treating refusals as a distinct UI state rather than just text prevents the user from hitting a dead end and abandoning the product.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T22:46:15.837267+00:00— report_created — created