AI-First
Yes, you should disclose AI-generated code, but in your contracts and your Git history, not with a badge. Transparency about who wrote AI code has been back in the spotlight since 2 August 2026, when Anthropic started invisibly watermarking what Claude produces. I train SMEs on Claude Code, and the question I now hear is: "Will my clients find out, and am I allowed to keep it from them?"
- 🔑 Invisible watermark: according to Anthropic, Claude has been flagging the text and files it generates since 2 August 2026.
- ⚠️ Limited proof: a detection proves contact with Claude, never who actually wrote the thing.
- 📊 Targeted obligation: Article 50 mainly covers providers, chatbots, deepfakes and text on matters of public interest.
- ✅ Simple policy: a contract clause, a Git trailer and a documented human review are enough for an SME.
In this article, I break down what the watermark actually does and what the AI Act requires (and doesn't). Then I share the four-step policy I use myself and recommend to clients.
What does Claude's watermark actually change?
Claude's watermark is an invisible, machine-readable signature added to text and files generated by Anthropic's models. It responds to Article 50 of the EU AI Act, which has applied since 2 August 2026. The effect is global: a user in Hanoi is affected just as much as a user in Lyon.
What exactly does Anthropic watermark?
According to Kyle Balmer's video (AI with Kyle), Anthropic has announced two mechanisms: a watermark built into the text itself, and provenance metadata on compatible files. A thread on r/AI_Agents adds that this covers the API, the web app, Claude Code and Cowork, with C2PA-signed metadata on .png, .jpg and .svg files. The same thread says older models are being watermarked retroactively.
Kyle Balmer also points out that the viral headline (nearly 12 million views on the original tweet) overstates things: not every response from every model can be publicly detected today. In his video on a Claude Code blogging skill, Daniel Agrici places the technique in the lineage of Google DeepMind's SynthID, which works by adjusting word choice.
The key point: the watermark is a technical layer, not a visible label.
What does a positive detection prove?
Next to nothing about authorship. Daniel Agrici's video lists the limits: copy-pasting keeps the watermark, light editing usually keeps it, a full rewrite removes it, and no public detector exists yet. A positive result proves Claude was involved somewhere, never that it wrote everything.
A writer on r/WritingWithAI takes the argument further: if you ask Claude to proofread, translate or reformat your own text, the output gets watermarked even though the ideas are yours. And the absence of a watermark doesn't prove a human wrote it either. On code, the sources I read say nothing about whether the watermark survives refactoring, so I won't claim it does.
What does the AI Act say about the code and text you deliver?
Article 50 of the EU AI Act sets transparency obligations for providers and deployers of generative AI systems. They cover watermarking content, telling people when they're interacting with an AI, and labelling deepfakes. The rules came into force on 2 August 2026.
Who's on the hook, the provider or the deployer?
On 10 June 2026, the European Commission published a two-part code of practice, as law firm DDG explains: the first part for providers (watermark content and make it detectable), the second for deployers (label deepfakes and text). On the official page for the Code of Practice on transparency of AI-generated content, the Commission states that signing up is voluntary but the Article 50 requirements remain legal obligations.
Anthropic is the provider: the watermark is its job. You, as an SME using Claude Code, are a deployer. TransparIA's guide, which summarises the code, notes that signing up doesn't prove compliance, that there's a proportionality clause for SMEs, and that the official icons (AI, AI-generated, AI-modified) are free to use.
Does an SME have to label the code it delivers?
I'm not a lawyer, but here's how I read the sources: deployer obligations target deepfakes, chatbots and text on matters of public interest generated without human review. A thread on r/HighTechFR relaying the French Ministry of the Economy's clarification sums up these cases well. None of the sources mention application code delivered to a client, and one post in that thread also points to an exemption for systems that only assist with standard editing.
My reading: delivered code isn't the focus of Article 50, but your client can reasonably ask you how it was produced.
| Situation | Obligation according to the sources | Who bears it | What I do |
|---|---|---|---|
| Watermarking Claude's output | Make the content detectable | Anthropic (provider) | Don't remove it |
| Customer chatbot on your site | Disclose that it's an AI | You (deployer) | Clear welcome message |
| Public-interest text with no review | State that it's AI-generated | You (deployer) | Documented human review |
| Deepfake in a business context | Official icon | You (deployer) | AI-generated icon |
| Code delivered to a client | Not mentioned in the sources I read | Contract | Clause and Git history |
SOURCE: European Commission, TransparIA, DDG, cited transcripts · UPDATED 10/2026
Why has AI code authorship become a matter of trust?
Because a technical watermark is no substitute for a human statement. It says "Claude touched this", not "here's who decided and who reviewed it". For a business owner, the question that matters is accountability: who answers for a bug in production? Real transparency is the kind that lets you trace a line of code back to a decision.
How are researchers and developers handling the question?
A post on r/LargeLanguageModels titled "Cyborg Scholars" claims that more than half of new software commits are now LLM-assisted, and that universities and journals are restricting model co-authorship on accountability grounds. I'd treat that figure with caution: it's a forum claim with no dated source.
The principle behind it is solid, though: every claim should be traceable to an accountable agent who stands behind it. That's exactly what I believe about agents in business: AI can read, decide and act, but human oversight has to stay at the centre.
How do you track who decided what on a project?
A workflow shared on r/ClaudeWorkflows presents "who-made-the-call", an open-source Claude Code plugin that logs decisions made by the AI or by the user, including the model's reasoning when it made the call. It tackles the real problem: all the small decisions nobody asked for.
In my review of Claude Code after six months with SME clients, the risk I see most often isn't bad code. It's code nobody can explain anymore.
Untraceable code becomes debt, whether a human or an AI wrote it.
What transparency policy can you put in place this afternoon?
Four steps are enough for an SME: an inventory of where you use AI, a contract clause, a Git trail and a documented human review. None of them needs a senior developer, and you can set them all up in half a day. I use them on my own projects and recommend them to the business owners I work with.
What are the four concrete steps?
- Take stock of where you use AI. List everywhere AI is involved: code, content, support. It's the same map of automatable tasks I recommend building anyway.
- Add a clause. In your contracts and quotes, include a sentence stating that AI tools (named) are used in production, with human review.
- Keep the Git trail. By default, Claude Code adds a
Co-Authored-Byline to the commits it creates. Don't strip it out: it's the most reliable way to declare authorship, because it survives refactoring. - Document the review. A code review or pull request approved by a named human is your real proof of oversight.
To get started, my Claude Code tutorial for SMEs shows how to set up your sessions. And if you want a framework on the development team side, the team at GoLive Software already works by these rules.
Should you try to remove the watermark?
No. Daniel Agrici says himself that he wants to be able to "remove this watermark" from his blog posts, and a full rewrite does the trick. I understand the instinct, since a watermark can feel like a stigma. But rewriting to improve a text is legitimate. Rewriting to erase a trace isn't.
My argument is commercial before it's legal: if your client later finds out you hid your use of AI, you lose the trust that AI's productivity gains were helping you earn.
My verdict: disclose, but disclose smartly
Disclose AI use in your code, through your contracts and in Git, and don't try to hide it or advertise it in a banner. Claude's watermark neither protects you nor incriminates you: it proves contact with AI, nothing more. Only your own traceability shows who made the decisions.
When is this verdict no longer enough?
As soon as you publish text on matters of public interest without review, deploy a chatbot or distribute synthetic content: at that point, Article 50 applies to you directly. I'd recommend talking to a lawyer then, because the sources I read are summaries, not legal advice. And if you want a broader starting point, my article on automating prospecting with Claude Code shows how I build these safeguards into a real project.
FAQ
Does Claude really watermark the code it generates?
According to Kyle Balmer's video and the threads cited, Anthropic has been watermarking text, code included, across the API, the web app, Claude Code and Cowork since 2 August 2026. The sources don't say how well the watermark holds up after refactoring, so your Git history remains the most reliable record.
Does a detection result prove an AI wrote everything?
No. According to the sources, Anthropic acknowledges that a detection doesn't prove authorship: it only shows that Claude was involved, including for proofreading, translating or reformatting. Conversely, the absence of a watermark doesn't prove a human wrote it, since a full rewrite can erase the signal.
Does my company need to label its code "AI-generated"?
Based on the sources I read, Article 50 of the AI Act targets synthetic content, chatbots, deepfakes and public-interest text generated without human review, not delivered application code. A contract clause and a Git trail are still good practice. If you're unsure about your situation, ask a lawyer.
When do these rules come into force?
The Article 50 transparency obligations have applied since 2 August 2026. On 10 June 2026, the European Commission published a voluntary code of practice to help providers and deployers comply, along with free official icons.
Vidéos YouTube
- Claude Is Hiding Watermarks in Your AI Text (What It Actually Means) — Kyle Balmer | AI with Kyle
- #48 A Jug of Settled-Down Juice: AI Guidelines on Transparency Obligations w/ Dr. João P. Quintais — The Binary Agora
- EU AI transparency rules begin & OpenAI Astra research breakthrough - Tech News (Aug 30, 2026) — The Automated Daily
- This Claude Code skill wrote my entire blog in one prompt — Daniel Agrici
Discussions Reddit
- Claude now watermarks all AI-generated text and files. Good news or bad news? — r/AI_Agents
- Claude's Watermark Proves AI Contact, Not AI Authorship — r/WritingWithAI
- Since 2 August, the AI Act imposes new transparency rules (in French) — r/HighTechFR
- Cyborg Scholars – AI-Authorship Norms, Software and Academia — r/LargeLanguageModels
- Track AI and User Decisions in Claude Code with the 'who-made-the-call' Plugin — r/ClaudeWorkflows