A fresh Hacker News thread is pulling back the curtain on one of Claude Code's most infuriating interface problems. Developer davidbjaffe posted an Ask HN question on June 24 asking what improvements users would most like to see in Anthropic's CLI tool, and his answer reveals a recurring nightmare: usage policy violations that strike without warning or explanation.

The Specific Grievance

According to davidbjaffe, the problem surfaces when working with scientific article PDFs. The code he's developing processes these documents, but somewhere in that workflow, content triggers a policy violation—and that's where things get ugly. "No info on the details are provided," he noted. Users get an error flag without any explanation of what crossed the line or why.

Why Restarting Doesn't Help

The most maddening part of this bug (or design choice) is its persistence. Davidbjaffe reports that once a violation triggers, you're stuck: "Whatever you do after that (without restarting or rewinding), you still get the error." This means developers lose their entire session context and have to manually reconstruct what they were working on just to continue coding.

Filing Issues Goes Nowhere

Davidbjaffe also pointed out that submitting an issue through official channels apparently leads nowhere productive. "But this must be happening to thousands of users," he argued—suggesting the problem is widespread enough that it should be a priority fix, yet the feedback loop appears broken.

Key Takeaways

  • Claude Code policy violations provide zero diagnostic information to users
  • The error persists across sessions until a full restart or rewind
  • Developers processing text-heavy content (like PDFs) hit this more frequently
  • Existing issue reporting channels aren't resolving these complaints

The Bottom Line

This isn't just an interface polish request—it's a fundamental usability failure. When developers can't debug why their tooling is blocking them, they're flying blind. Anthropic needs to either make policy violations transparent or provide better escape hatches for recovery. Until then, expect more frustrated devs venting on HN.