In a rapid six-week sprint leading up to the August 2 enforcement date, the European Commission released three critical documents aimed at clarifying transparency obligations under Article 50 of the EU AI Act. These documents – the Code of Practice on marking and labelling of AI-generated content, the Commission Opinion assessing that Code, and the transparency guidelines for providers and deployers – provide a necessary framework for standard AI interactions. But for the growing cohort of developers building autonomous AI agents, they contain a structural gap: none of them address the unique operational realities of agentic systems.
The timeline tells the story of a Commission racing to build compliance infrastructure before a hard deadline. The Code of Practice on marking and labelling published June 10, the Commission Opinion assessing the Code followed on July 9, and the transparency guidelines landed July 20. Three documents in forty days, each addressing a different facet of the same obligation set. The sprint reflects genuine institutional urgency – the obligations apply August 2 regardless of whether firms have signed the voluntary Code or whether the Digital Omnibus has deferred other high-risk deadlines.
What the documents cover is clear and actionable. The transparency guidelines lay out provider obligations: inform users when they are directly interacting with an AI system, and implement machine-readable markings that make AI-generated or manipulated content detectable. Deployer obligations include disclosing the use of emotion-recognition or biometric-categorisation systems, identifying deepfakes, and labelling AI-generated text published for public interest purposes when the human-review exception does not apply. These are precise, implementable requirements for chatbots, content generators, and image synthesis tools – the class of AI systems that dominated the regulatory imagination when the AI Act was drafted.
What the documents do not cover is the class of AI systems that now dominates the market. Autonomous agents operate on a fundamentally different interaction model than chatbots or content generators. They plan across multiple steps, invoke external tools, make intermediate decisions without returning to the user, and increasingly communicate with other agents. The existing transparency framework assumes a linear interaction: a user asks, the AI responds, and disclosure attaches to that exchange. An agent that researches a topic across five sources, drafts a document, and submits it to a third-party platform has performed multiple transparency-relevant actions – but the guidelines offer no guidance on where disclosure attaches in that chain.
The EU AI Office has acknowledged this gap indirectly. Its AI Service Desk FAQ describes agent considerations as “only preliminary.” The pending draft standards prEN 18228 and prEN 18282 may eventually fill the space, but neither has been published. The Art. 50 Code of Practice, now published, addresses marking and labelling but does not grapple with autonomous decision-making as a distinct transparency challenge.
This is not a failure of intent but a failure of timing. The AI Act was negotiated and drafted before the agent wave made autonomous systems commercially mainstream. The transparency obligations in Article 50 are broad enough to cover agents – they apply to all AI systems that interact with natural persons or generate content. But the implementing guidance was written for the systems that existed when the framework was designed. The result is that agent builders must comply with obligations whose technical interpretation for their specific systems has not been clarified.
The convergence with California sharpens the question. SB 942 becomes operative on August 2 – the same day as Article 50. Both jurisdictions are imposing transparency requirements on AI systems. Neither has published agent-specific guidance. For builders shipping products that operate across both markets, this means designing compliance architectures for frameworks that structurally assume non-agentic systems, with the knowledge that the first enforcement actions will set precedent for how these obligations actually apply to autonomous workflows.
The practical path for builders is not to wait. With thirteen days until enforcement and no agent-specific guidance coming before that date, the responsible approach is to interpret the existing obligations through the lens of their stated purpose: ensuring that humans can identify when they are interacting with AI and when content has been AI-generated. For agents, that means building disclosure into the system at every point where an autonomous action affects a human-visible outcome – not because the guidelines say to, but because the underlying regulatory logic demands it. The Commission will eventually publish guidance for agentic systems. The question is whether builders will have built the infrastructure by then, or will be retrofitting it under enforcement pressure.