Who owns the code Claude Code wrote? Here's what developers need to know.

Hacker News is on fire right now with a simple question: Who owns the code Claude Code wrote?

280 points. 309 comments. And growing.

The thread is a mess of opinions, half-remembered copyright law, and genuine developer anxiety. Let me cut through it.

The short answer

Nobody is sure. And that uncertainty is the whole problem.

Here's the current landscape:

Scenario	Likely outcome	Certainty
You wrote 90%, Claude suggested 10%	You own it	High
Claude wrote 90%, you accepted it all	Unclear	Low
Enterprise Claude Code with IP indemnity	Anthropic covers you	Medium
Free/personal Claude Code	On you	Very low

What the Anthropic ToS actually says

Anthropics Terms of Service (Section 4) says: "Subject to your compliance with these Terms, Anthropic assigns to you all its right, title, and interest in and to Output."

Sounds good, right? Except:

1. "assigns" doesn't mean "guarantees copyright" — Anthropic can only assign what it owns
2. US Copyright Office has stated AI-generated content has no human author and therefore no copyright
3. This is being actively litigated in multiple jurisdictions

The practical implication: code that has no copyright owner is in the public domain. Anyone can copy it. Including your competitors.

The enterprise escape hatch

If you're using Claude Code on the enterprise plan ($25+/seat/month), Anthropic offers IP indemnity — they'll defend you if someone claims your Claude-generated code infringes their IP.

But that's indemnity from input claims (training data), not the ownership question about output.

These are different problems.

What actually matters for most developers

For the vast majority of real-world usage, the ownership question is theoretical:

• Internal tools: nobody's suing you over internal automation code
• Startup MVPs: get to revenue before worrying about IP
• OSS contributions: already in the public domain conversation
• Client work: this is where it gets real — put language in your contracts

The developers who have the most exposure are:

• Selling a SaaS product built heavily with AI assistance
• Working in regulated industries (fintech, health, defense)
• Contributing to projects with strict IP provenance requirements (Linux kernel, etc.)

The real risk nobody's talking about

It's not the ownership question. It's the audit question.

If you're in a due diligence process (acquisition, funding, IPO), someone is going to ask: "How was this code written? What's your AI policy?"

Right now, most developers have no answer. No policy. No records. Just Slack messages saying "I ran it through Claude."

That's the gap that will actually hurt companies.

What to do right now

1. Document your AI usage — which files, which tools, what percentage
2. Add an AI disclosure to your contracts — especially client work
3. Keep meaningful human review — the more you understand and modify the output, the stronger your ownership claim
4. Check your employer's policy — many enterprise companies have blanket "no AI tools" policies you may be violating

The $20/month dimension nobody mentions

Here's an uncomfortable truth from the HN thread: the developers most exposed to the ownership ambiguity are the ones using the most Claude Code — and Claude Code at enterprise pricing ($25+/seat) has IP indemnity.

The personal/free tier doesn't.

If you're a solo developer in the Philippines (₱1,120/month for ChatGPT), Nigeria (₦32,000/month), or India (₹1,600/month), you can't afford the enterprise tiers that come with IP protection.

This creates a two-tier system:

• Rich developers get IP protection
• Everyone else is on their own

For developers who need Claude access without the enterprise price tag, SimplyLouie provides Claude API access at ₹165/month (India), ₱112/month (Philippines), or $2/month globally — without the enterprise overhead.

The ownership question is the same either way. But at least you're not paying $25/seat to navigate it.

The actual answer

Until courts settle this (probably 2028-2030), the practical answer is:

Write code with AI. Review it seriously. Modify it meaningfully. Document what you did. Talk to a lawyer before an acquisition.

The developers asking "who owns this?" are at least asking the right question. The ones who will get hurt are the ones who never thought to ask.

---

What's your company's AI code policy? Drop it in the comments — I'm genuinely curious what real policies look like in practice.