claude-code - 💡(How to fix) Fix [Bug] Anthropic API Error: Output blocked by content filtering policy [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#47052Fetched 2026-04-13 05:42:45
View on GitHub
Comments
0
Participants
1
Timeline
5
Reactions
0
Participants
Timeline (top)
labeled ×5

Error Message

❯ I don't understand how come this issue is only visible in documentation page. fill the doc page with some 'lorem ipsum' to check your hypothesis.

Read 1 file (ctrl+o to expand)

⏺ Bash(which zola && zola --version) ⎿  /opt/homebrew/bin/zola zola 0.22.1

⏺ I'll add lorem ipsum to the documentation page and rebuild so you can compare. ⎿  API Error: Output blocked by content filtering policy

✻ Worked for 26s

Code Example

I don't understand how come this issue is only visible in documentation page.
   fill the doc page with some 'lorem ipsum' to check your hypothesis.

  Read 1 file (ctrl+o to expand)

Bash(which zola && zola --version)
  ⎿  /opt/homebrew/bin/zola
     zola 0.22.1

I'll add lorem ipsum to the documentation page and rebuild so you can compare.
    API Error: Output blocked by content filtering policy

Worked for 26s

---

[{"error":"Error: {\"type\":\"error\",\"error\":{\"details\":null,\"type\":\"invalid_request_error\",\"message\":\"Output blocked by content filtering policy\"},\"request_id\":\"req_011CbWYp22Y864uHoBmCJ8hy\"}\n    at T (/$bunfs/root/src/entrypoints/cli.js:14:2015)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-05-29T08:32:11.879Z"},{"error":"Error: {\"type\":\"error\",\"error\":{\"details\":null,\"type\":\"invalid_request_error\",\"message\":\"Output blocked by content filtering policy\"},\"request_id\":\"req_011CbWYrFHoi9CD6Y2Pk6SFk\"}\n    at T (/$bunfs/root/src/entrypoints/cli.js:14:2015)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-05-29T08:32:43.184Z"}]
RAW_BUFFERClick to expand / collapse

Bug Description I ask claude to add some dummy text in a html template file, to debug a potential CSS issue.

❯ I don't understand how come this issue is only visible in documentation page.
   fill the doc page with some 'lorem ipsum' to check your hypothesis.

  Read 1 file (ctrl+o to expand)

⏺ Bash(which zola && zola --version)
  ⎿  /opt/homebrew/bin/zola
     zola 0.22.1

⏺ I'll add lorem ipsum to the documentation page and rebuild so you can compare.
  ⎿  API Error: Output blocked by content filtering policy

✻ Worked for 26s

but nothing happened...?

Environment Info

  • Platform: darwin
  • Terminal: ghostty
  • Version: 2.1.142
  • Feedback ID: 50043c69-f174-4e64-9e0d-4b474d337649

Errors

[{"error":"Error: {\"type\":\"error\",\"error\":{\"details\":null,\"type\":\"invalid_request_error\",\"message\":\"Output blocked by content filtering policy\"},\"request_id\":\"req_011CbWYp22Y864uHoBmCJ8hy\"}\n    at T (/$bunfs/root/src/entrypoints/cli.js:14:2015)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-05-29T08:32:11.879Z"},{"error":"Error: {\"type\":\"error\",\"error\":{\"details\":null,\"type\":\"invalid_request_error\",\"message\":\"Output blocked by content filtering policy\"},\"request_id\":\"req_011CbWYrFHoi9CD6Y2Pk6SFk\"}\n    at T (/$bunfs/root/src/entrypoints/cli.js:14:2015)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-05-29T08:32:43.184Z"}]

extent analysis

TL;DR

The issue is likely due to a content filtering policy blocking the output, and a workaround may involve modifying the request to avoid triggering this policy.

Guidance

  • Review the API request being made to ensure it does not contain keywords that could trigger the content filtering policy.
  • Verify that the API endpoint and parameters are correctly configured and do not inadvertently include restricted content.
  • Consider adding logging or debugging statements to capture the exact request being sent to the API to identify potential triggers for the filtering policy.
  • If possible, test the API request with a minimal or dummy payload to isolate if the issue is with the request itself or the content being sent.

Example

No code example is provided as the issue does not include sufficient details about the API request or the code being used.

Notes

The exact cause of the issue is uncertain without more information about the API request and the content filtering policy. The provided error messages suggest that the issue is related to the policy, but the specifics of the request and the policy's rules are not clear.

Recommendation

Apply workaround: Modify the API request to avoid triggering the content filtering policy, as the exact cause of the issue is related to the policy and not a version or upgrade issue.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING