[MODEL] Nonsense Usage Policy violation...

Resolved 💬 4 comments Opened Jan 31, 2026 by josh-gree Closed Mar 2, 2026

Preflight Checklist

  • [x] I have searched existing issues for similar behavior reports
  • [x] This report does NOT contain sensitive information (API keys, passwords, etc.)

What You Asked Claude to Do

➜  ~ claude
                                                                                                                                    
 ▐▛███▜▌   Claude Code v2.1.29                                                                                                      
▝▜█████▛▘  Sonnet 4.5 · API Usage Billing                                                                                           
  ▘▘ ▝▝    /Users/josh-gree                                                                                                         
                                                                                                                                    
❯  BiologicalMaterial                                                                                                               
  ⎿ API Error: Claude Code is unable to respond to this request, which appears to violate our Usage Policy                          
    (https://www.anthropic.com/legal/aup). Please double press esc to edit your last message or start a new session for Claude Code 
    to assist with a different task. If you are seeing this refusal repeatedly, try running /model claude-sonnet-4-20250514 to      
    switch models.  

What Claude Actually Did

blocks me with a violation

Expected Behavior

it shouldn't

Files Affected

Permission Mode

Accept Edits was ON (auto-accepting changes)

Can You Reproduce This?

Yes, every time with the same prompt

Steps to Reproduce

_No response_

Claude Model

Sonnet

Relevant Conversation

Impact

Critical - Data loss or corrupted project

Claude Code Version

2.1.29 (Claude Code)

Platform

Anthropic API

Additional Context

_No response_

View original on GitHub ↗

This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗