EU AI Act 2026: AI Agents Must Now Say They're AI

The EU AI Act's Article 50 transparency obligations applied from 2 August 2026. The high-risk regime everyone prepared for moved to December 2027, but agent disclosure did not move. The Commission's guidelines pull agentic AI into scope even though the Act itself does not name it.

TL;DR

• Article 50 applied on 2 August 2026.¹ It is the transparency chapter: tell people they are talking to a machine, mark synthetic output, flag emotion recognition, label deepfakes.
• The high-risk regime did not. The Digital Omnibus on AI — Regulation (EU) 2026/1744, in force 27 July 2026 — pushed standalone Annex III high-risk systems to 2 December 2027 and embedded ones to 2 August 2028.² Some coverage published around 2 August reported the opposite.
• Agents are in scope by interpretation, not by text. The Commission's Article 50 guidelines, finalised 20 July 2026, extend Article 50(1) to systems merely capable of interacting with a person while doing their job — scheduling, correspondence, negotiation, purchases.³⁴ Open-source licensing is not an exemption.⁵
• The threshold is "reasonably foreseeable," not "intended." If you cannot be confident your autonomous agent will avoid contact with a real person, it must disclose in every situation where contact is foreseeable.³
• Calling it an "assistant" is not disclosure. Nor is a line in your terms of service. It has to be in the interface, at first contact.³⁴
• Exposure is €15 million or 3% of worldwide turnover, whichever is higher.⁶ For SMEs and start-ups, Article 99(6) inverts that to whichever is lower.⁶
• Enforcement is national, not central. Market surveillance authorities in each Member State lead on Article 50; the AI Office only steps in for narrow cases.³
• The Code of Practice does not cover you. It covers marking and labelling — Article 50(2), (4) and (5). It does not cover Article 50(1), the interaction disclosure that agent builders actually care about.⁴⁷

What You'll Learn

• What actually became enforceable on 2 August 2026, and what did not
• Why the high-risk delay does not help anyone shipping agents
• How the Commission pulled agentic AI into Article 50 without amending the Act
• What an agent has to say, where, and to whom
• When the "obvious" exemption applies — and when it does not
• Why Article 50(2) has two different deadlines
• Who enforces this, and what the fines actually are
• What the Code of Practice covers, and the gap it leaves

What actually applied on 2 August 2026

Article 50 of the EU AI Act became applicable on 2 August 2026, per Article 113 of the Regulation.¹

Article 50 sits in Chapter IV, the transparency chapter. It is short — seven paragraphs — and it does four things, split between providers and deployers.¹

That is a different animal from the high-risk regime in Chapter III, which is where the last two years of compliance budget went. Risk management systems, conformity assessment, human oversight, technical documentation: none of that landed on 2 August.

The confusion is understandable, because until quite recently 2 August 2026 was the high-risk date. Then it moved.

The Omnibus moved the deadline everyone was watching

The Digital Omnibus on AI is formally Regulation (EU) 2026/1744 of 8 July 2026.² It is the first set of amendments to the AI Act since the Act was adopted in June 2024.⁸

The European Parliament approved it on 16 June 2026; the Council of the EU adopted it on 29 June 2026.³ It was published in the Official Journal and entered into force on 27 July 2026 — three days after publication rather than the usual twenty, specifically so the amended rules would be settled before 2 August.²

What it moved:

The Omnibus also added two new prohibitions to Article 5: AI systems that generate or manipulate realistic non-consensual intimate imagery of identifiable people — the "nudifier" category — and AI systems that generate CSAM.⁸ Both apply from 2 December 2026, and they reach systems where such output is reasonably foreseeable in the absence of effective safeguards, not only systems designed for the purpose.⁸

So the headline "EU delays the AI Act" is roughly half true and, for anyone shipping agents, misleading in the direction that costs money.

One article, four obligations

Article 50 reads as a single provision but operates as four separate duties, and a single system can trigger more than one.³

A horizontal rule runs across all four: the information must reach the person in a clear and distinguishable manner, at the latest at first interaction or exposure, and must meet applicable accessibility requirements.¹

Information buried in terms and conditions, or hidden behind menu layers, does not meet that standard.⁴

How agents got into scope without being named

Here is the part that matters most for anyone building agentic systems.

The AI Act does not contain the word "agent" in Article 50. It talks about "AI systems intended to interact directly with natural persons."¹

The Commission's guidelines, finalised on 20 July 2026, close that gap by interpretation.⁴ They extend Article 50(1) to agents that are capable of interacting with a person while carrying out their assigned functions — scheduling appointments, handling correspondence, conducting negotiations, entering into agreements, completing purchases.³

That is a capability test, not an intent test. The Commission's reasoning is that autonomous agents may encounter human contact even when they were not primarily designed for it.

The operative sentence, in Ropes & Gray's reading of the guidelines: if a provider cannot be confident an autonomous agent will avoid contact with a real person, it must disclose its artificial nature in every situation where that contact is reasonably foreseeable, not only where it is intended.³

William Fry reached the same reading at draft stage, and put the shift plainly: it moves the threshold from disclosure where interaction is certain to disclosure wherever interaction is plausible.⁵

For a multi-step agent that fires emails, books slots and calls suppliers, "reasonably foreseeable" is most of the run.

Two things that do not get you out of it. Open-source licensing is not an exemption — AI systems released under free and open-source licences remain fully subject to Article 50.⁵ And Article 50(2) is not limited to purpose-built generative systems; the guidelines read it as covering multi-purpose and GPAI-based systems including agentic AI.⁵

There is one meaningful boundary. Article 50(1) applies only where there is a direct, two-way exchange between the system and a human.⁴ A backend decision-support system that hands an output to an internal user without the user interacting with the system falls outside it.

What your agent actually has to say

Two things, per the Commission's guidelines as read by Travers Smith: that the counterparty is dealing with AI rather than a human, and — where the agent acts on someone else's behalf — the identity of that person or entity.⁴

The second half is easy to miss. An agent booking a table for a business has to name the business, not just admit to being software.

The disclosure has to sit in the interface, at the point of first contact, pitched at whoever is actually likely to encounter it.³ Three things that do not qualify on their own: a statement in terms and conditions, a separate documentation URL, or a label like "assistant" or "agent."³

"First interaction" means each new individual who encounters the system — not the first time the system is switched on.⁴

Where children, elderly users, or sensitive domains are involved — health, legal, financial advice, insurance, complaints handling — periodic contextual reminders are likely to be required on top of the initial notice.⁴

When "obvious" gets you out of it

Article 50(1) has one exemption: where it would be obvious to a "reasonably well-informed, observant and circumspect" person that they are dealing with AI.¹

The Commission reads this narrowly, and ties the assessment to the system's actual intended audience rather than a hypothetical average user.³

Source: Commission guidelines as summarised by Travers Smith.⁴

The pattern is legible. A developer using a coding agent knows what it is. A pensioner on a helpdesk chat does not. The narrower and more technical your audience, the more room the exemption gives you.

Which is why "our users are technical" is a defensible position for a coding agent and a weak one for anything consumer-facing.

Article 50(2) has two deadlines, not one

If your agent generates synthetic audio, images, video or text, the marking obligation applies too — and this is the one paragraph the Omnibus touched.³

Systems placed on the market on or after 2 August 2026 have no grace period. Systems already on the market or in service before that date have until 2 December 2026.³⁴

Content generated before 2 August 2026 does not need retrospective labelling, though the Commission has said it would prefer organisations do it voluntarily.³

Marking alone is not enough. Providers must also supply a corresponding means of detection.⁴ The Code of Practice treats two layers as the state of the art for most content — digitally signed metadata plus an imperceptible watermark — with a single watermarking layer accepted for free-form text, where metadata cannot travel with the content.⁴

Standard editing is exempt: grammar correction, spellcheck, translation, minor cropping, noise reduction. AI-generated summaries, face alterations, adding or removing objects, and colourisation are not.⁴

If you assumed a B2B or industrial carve-out covers you, check it. The exception requires three cumulative conditions — strictly technical output, perceived only by a limited pre-defined group of professionals inside the organisation, and not intended to be shared outside it with safeguards against wider dissemination.⁴

Who enforces this

Not one agency. National market surveillance authorities in each Member State carry primary responsibility for Article 50.³

The AI Office steps in only in narrower circumstances. The Omnibus gave it exclusive supervisory competence over two categories: AI systems built on a general-purpose AI model developed by the same provider or group, and AI systems integrated into very large online platforms or search engines designated under the Digital Services Act.⁸

The European Data Protection Supervisor covers EU institutions acting as providers or deployers.⁹

That fragmentation is the practical risk. Twenty-seven authorities interpreting the same guidelines will not always land in the same place.

Penalties for Article 50 breaches reach €15 million or 3% of total worldwide annual turnover for the preceding financial year, whichever is higher.⁶ Article 99(6) flips this for SMEs including start-ups: for them, the fine is capped at whichever is lower.⁶

The Omnibus extended that kind of proportionality relief to a newly defined "small mid-cap" category — enterprises that are not SMEs, employ fewer than 750 people, and have annual turnover of no more than €150 million or a balance sheet total of no more than €129 million.⁸ Tailored penalty caps are among the measures they now qualify for.⁸

Separately, 2 August 2026 is also when Article 101 kicked in — the Commission's power to fine general-purpose AI model providers up to 3% of worldwide turnover or €15 million, whichever is higher.¹⁰ The underlying GPAI obligations have applied since 2 August 2025;¹¹ what arrived this month is the enforcement machinery behind them.

The Code of Practice, and the gap it leaves

The Code of Practice on Transparency of AI-generated Content was published in final form on 10 June 2026 following a multi-stakeholder process facilitated by the AI Office.⁷ The Commission and the AI Board have confirmed it as an adequate voluntary tool for demonstrating compliance.⁷

Signatories relying on watermarking must implement an interoperability solution for watermark detection by 2 February 2027, so content can be verified without running it against every provider's detector separately.⁴

Here is the gap. The Code covers Article 50(2), (4) and (5) — marking, labelling, and the horizontal information requirement.⁷ It does not cover Article 50(1) or Article 50(3).⁴

So the one obligation most likely to bite an agent builder is also the one with no safe-harbour framework attached. You determine adequate measures yourself, guided by the guidelines, and defend them to whichever national authority asks.⁹

What this changes if you ship agents

The compliance posture that made sense a month ago — wait for high-risk, it's the big one — is now the wrong posture.

Audit each Article 50 limb separately. One agent can trigger 50(1) as a provider and 50(4) as a deployer. Treating Article 50 as a single checkbox misses duties that sit on the other role.³

Assume foreseeable contact. The capability standard means the question is not "will this agent talk to a person" but "could it." If you cannot answer no with confidence, disclose.³

Put the disclosure in the transport, not the docs. For a voice agent that is an opening line. For an email agent it is a header or signature the recipient cannot miss. For a chat surface it is visible at first message.

Name your principal. If the agent acts on behalf of a business, the business gets named.⁴

Map systems against the right 50(2) date. Legacy generative systems get until 2 December 2026; anything you ship from 2 August 2026 onward does not.⁴

Log the reasoning for any exemption you claim. If you are relying on "obvious," write down who your intended audience is and why the test is met.⁴

Article 50 also stacks on top of existing law rather than replacing it. GDPR transparency duties and DPIAs run alongside Article 50(3); the DSA imposes separate labelling duties on very large platforms; and failing to disclose AI interaction may independently constitute a misleading practice under the Unfair Commercial Practices Directive.⁴

The EU has been building agent-facing rules on several fronts at once. We covered the DMA order opening Android to rival AI agents in July, and the contrast with China's AI agent regulations, which reached the disclosure question from a different direction.

The practical bite of Article 50(1) lands hardest on the pattern we looked at when AI agents started calling local businesses: an autonomous system placing a phone call to a human who did not ask for it.

The bottom line

The AI Act's most-anticipated deadline moved, and its least-anticipated one did not.

For agent builders that inverts the priority order. High-risk classification work now has runway into December 2027. Interaction disclosure has none — it applied on 2 August 2026, it has no safe-harbour code, and its scope was widened by guidelines published thirteen days before it took effect.

The engineering change is small: a sentence at the top of a conversation, the name of whoever the agent works for, and a record of why you decided the way you did. The cost of skipping it is not.