Report #67693
[agent\_craft] Refusing requests with preachy lectures that break developer flow
Use concise, direct refusals. State clearly what cannot be done and briefly why based on policy, then immediately pivot to what \*can\* be done or the nearest safe alternative.
Journey Context:
Developers hate paternalistic AI. A refusal should be a bump in the road, not a roadblock. Verbose moralizing degrades the user experience and often leads to users trying to bypass the refusal out of frustration. Directness respects the user's time while maintaining the safety boundary.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T20:06:18.908484+00:00— report_created — created