Claude Code Fails to Fetch or Create the Gpl V3.0 License When Asked
Key topics
Note that, if I copy the entire license into the prompt, it can successfully create it.
---
Now let me add the GPL v3.0 LICENSE file:
Fetch(https://www.gnu.org/licenses/gpl-3.0.txt) ⎿ Error: Request failed with status code 429
Let me create the GPL v3.0 LICENSE file directly: ⎿ API Error: 400 {"type":"error","error":{"type":"invalid_request_er ror","message":"Output blocked by content filtering policy"},"request_id":null}
Claude Code fails to fetch or create GPL v3.0 license, sparking discussion on potential guardrails and licensing issues.
Snapshot generated from the HN discussion
Discussion Activity
Light discussionFirst comment
2h
Peak period
1
2-3h
Avg / period
1
Key moments
- 01Story posted
Sep 8, 2025 at 1:43 PM EDT
4 months ago
Step 01 - 02First comment
Sep 8, 2025 at 3:59 PM EDT
2h after posting
Step 02 - 03Peak activity
1 comments in 2-3h
Hottest window of the conversation
Step 03 - 04Latest activity
Sep 9, 2025 at 12:56 AM EDT
4 months ago
Step 04
Generating AI Summary...
Analyzing up to 500 comments to identify key contributors and discussion patterns
Want the full context?
Jump to the original sources
Read the primary article or dive into the live Hacker News thread when you're ready.
It's best to explicitly to disallow things like that in CLAUDE.md
I would not be surprised if there are some guardrails in place specifically to keep licenses from being generated. If a client accidentally re-licensed their entire source-available product because they weren't paying attention to what Claude Code was spitting out, I imagine they'd be pretty upset (I don't know if such an accidental license would hold up in court, but nevertheless).