claude-code - 💡(How to fix) Fix [Bug] Anthropic API Error: Content Filtering Policy blocks AGPLv3 LICENSE file creation [1 participants]

[{"error":"Error: NON-FATAL: Lock acquisition failed for /home/ben/.local/share/claude/versions/2.1.126 (expected in multi-process scenarios)\n at n68 (/$bunfs/root/src/entrypoints/cli.js:2770:2177)\n at sM6 (/$bunfs/root/src/entrypoints/cli.js:2770:1257)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-05-04T12:36:25.519Z"},{"error":"Error: Request was aborted.\n at makeRequest (/$bunfs/root/src/entrypoints/cli.js:50:3448)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-05-04T13:13:35.936Z"},{"error":"Error: 400 {"type":"error","error":{"type":"invalid_request_error","message":"Output blocked by content filtering policy"},"request_id":"req_011CahbFdPnRUMQxbUpmUeFk"}\n at generate (/$bunfs/root/src/entrypoints/cli.js:11:57082)\n at makeRequest (/$bunfs/root/src/entrypoints/cli.js:50:4943)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-05-04T13:16:54.986Z"}]

TL;DR

The issue is likely due to a content filtering policy blocking the addition of an AGPLv3 LICENSE file, and a workaround may involve modifying the file content or checking the policy settings.

Guidance

• The error messages suggest a content filtering policy is blocking the request, so reviewing and adjusting this policy may resolve the issue.
• The "Lock acquisition failed" error could be related to a multi-process scenario, but it's unclear if this is directly related to the content filtering policy error.
• Checking the request ID ("req_011CahbFdPnRUMQxbUpmUeFk") may provide more information about the specific policy or error.
• Consider modifying the LICENSE file content to see if it triggers the content filtering policy, or try adding the file through a different method.

Example

No code snippet is provided as the issue does not clearly imply a specific code change.

Notes

The issue lacks information about the specific content filtering policy and its settings, making it difficult to provide a more detailed solution.

Recommendation

Apply workaround: The issue seems to be related to a content filtering policy, and modifying the file content or checking the policy settings may resolve the issue.