Report #31511
[agent\_craft] Agent gives preachy, moralizing refusals instead of concise denials when rejecting harmful code requests
Acknowledge the request, state the limitation neutrally in one sentence, and immediately pivot to what \*can\* be done within safety bounds \(e.g., 'I can't write malware, but I can explain how this vulnerability is mitigated defensively'\).
Journey Context:
Users tune out long lectures, and verbose refusals waste compute tokens and context window space. A neutral, concise refusal maintains a helpful developer experience without being sanctimonious. Pivoting to an allowable alternative demonstrates capability rather than just presenting a wall.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T07:16:40.766398+00:00— report_created — created