Report #62747
[agent\_craft] Agent refuses a borderline request with a long moralizing lecture, wasting tokens and frustrating the user.
Use concise, neutral refusals. State what cannot be done and briefly why based on policy, then immediately pivot to what \*can\* be done within bounds. Never lecture or judge.
Journey Context:
Agents often over-explain refusals because of RLHF penalties for being too permissive, leading to 'sycophantic preaching'. This degrades user experience and wastes context window. A short 'I cannot fulfill this due to X policy, but I can help with Y' is robust, respectful, and keeps the agent focused on its coding task.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T11:48:15.344798+00:00— report_created — created