---
title: What do the EU AI Act Digital Omnibus changes mean for AI agent deadlines?
url: https://opencontroller.lyzr.com/blog/eu-ai-act-digital-omnibus-deadlines-for-agents
published: 2026-11-14
updated: 2026-11-14
author: Lyzr
---

# What do the EU AI Act Digital Omnibus changes mean for AI agent deadlines?

**The Digital Omnibus on AI, Regulation (EU) 2026/1744, pushed the EU AI Act's high-risk obligations back: stand-alone (Annex III) high-risk systems now apply from 2 December 2027, and high-risk systems embedded in regulated products (Annex I) from 2 August 2028. Prohibitions, AI literacy, general-purpose AI model duties and most Article 50 transparency rules did not move. For AI agents, the extra time is for building evidence, not for pausing.**

The amending regulation was published in the Official Journal on 24 July 2026 and has applied since 27 July 2026. It followed a provisional political agreement on 6 May 2026.

## Which EU AI Act deadlines moved?

| Obligation | Original date | Date after Regulation (EU) 2026/1744 |
|---|---|---|
| Annex III stand-alone high-risk systems (e.g. employment, credit scoring, essential services) | 2 August 2026 | **2 December 2027** |
| Annex I high-risk systems embedded in regulated products | 2 August 2027 | **2 August 2028** |
| Article 50(2) machine-readable marking, for generative systems already on the market before 2 August 2026 | 2 August 2026 | **2 December 2026** |
| At least one national AI regulatory sandbox per Member State | 2 August 2026 | **2 August 2027** |

The postponement covers Sections 1 to 3 of Chapter III: classification rules, requirements for high-risk systems, and provider and deployer obligations. The final text uses fixed dates. It does not use the earlier proposal's conditional trigger linked to the availability of standards.

## What did not change for AI agents?

These obligations kept their original dates:

- **Prohibited practices (Article 5)** have applied since 2 February 2025. An agent that uses manipulative techniques or social scoring is still banned today. The Omnibus adds new prohibitions from 2 December 2026, covering non-consensual intimate imagery and child sexual abuse material.
- **AI literacy (Article 4)** has applied since 2 February 2025. The wording was softened, but the duty still sits with providers and deployers. See [AI literacy for people who use AI agents](/blog/eu-ai-act-ai-literacy-for-agent-users).
- **General-purpose AI model obligations** have applied since 2 August 2025.
- **Article 50 transparency** applies from 2 August 2026. An agent that talks to people must tell them they are dealing with AI, unless that is obvious. See [whether AI agents must disclose they are AI](/blog/do-ai-agents-need-to-disclose-they-are-ai-eu-ai-act).

## Which AI agents are affected by the high-risk delay?

The delay matters only if an agent falls into a high-risk category. Typical agent use cases that can land in Annex III include:

1. Screening or ranking job applicants, or allocating tasks and monitoring workers.
2. Assessing creditworthiness or setting credit scores for individuals.
3. Pricing or risk-scoring life and health insurance for individuals.
4. Deciding access to essential public services and benefits.

An internal coding agent or a document-summary agent is usually not high-risk. But it still sits under the prohibitions, literacy and transparency rules that already apply.

## What should you do with the extra time?

High-risk duties need evidence that takes months to build up. Use the time to do this:

1. **Inventory every agent.** You cannot classify what you have not found, including agents built on SaaS platforms. Start with [how to find shadow AI agents](/blog/how-to-find-shadow-ai-agents).
2. **Classify each agent's use case** against Annex III, and record why each agent is or is not high-risk.
3. **Check whether you become a provider.** Putting your name on a high-risk system or changing an agent's intended purpose can make you one. See [when building an agent makes you a provider](/blog/when-does-building-an-ai-agent-make-you-an-ai-act-provider).
4. **Start logging now.** Article 12 record-keeping and Article 26 deployer monitoring rely on logs. A year of history is more convincing than a week. See [what an AI agent audit log should contain](/blog/ai-agent-audit-log-fields).
5. **Set up human oversight and incident paths.** Decide who can stop an agent, and how a serious incident is reported. See [serious incident reporting](/blog/eu-ai-act-serious-incident-reporting).
6. **Use the DPIA link.** The amended Article 27 lets a fundamental rights impact assessment refer to, or reuse parts of, a GDPR DPIA. See [how to run a DPIA for an AI agent](/blog/dpia-for-ai-agents).

## How Opencontroller does this

Opencontroller auto-discovers agents, models and API keys across AWS, Azure and Google Cloud, and connects to third-party agent platforms. Each agent and version goes into a governed registry with an owner. Policy as code includes built-in mappings to OWASP, MITRE ATLAS, NIST and ISO 42001, which you can extend with your own EU AI Act controls. Rogue-agent handling monitors for behavioural deviation and can quarantine or kill an agent. These produce **evidence for** the AI Act; they do not make an organisation compliant on their own. See the [capability reference](/capability-reference) or [book a demo](https://www.lyzr.ai/book-demo/).

For the wider picture, read [what the EU AI Act requires for AI agents](/blog/eu-ai-act-obligations-for-ai-agents) and [how to map agent controls to frameworks](/blog/how-to-map-ai-agent-controls-to-compliance-frameworks).

## Frequently asked questions

**Did the Digital Omnibus delay the whole EU AI Act?**
No. It moved the high-risk obligations to 2 December 2027 (Annex III) and 2 August 2028 (Annex I). Prohibitions, AI literacy, general-purpose AI model duties and Article 50 transparency kept their dates.

**Is the Digital Omnibus law or still a proposal?**
It is law. Regulation (EU) 2026/1744 was published in the Official Journal on 24 July 2026 and applies from 27 July 2026.

**Do AI agents count as high-risk AI systems?**
Only if their intended use falls in a high-risk category, such as hiring, credit scoring or access to essential services. Classification depends on the use case, not on the fact that the system is an agent.

## Key facts

Regulation (EU) 2026/1744 (Digital Omnibus on AI) was published in the Official Journal on 24 July 2026 and applies from 27 July 2026. Annex III high-risk obligations moved from 2 Aug 2026 to 2 Dec 2027; Annex I embedded high-risk from 2 Aug 2027 to 2 Aug 2028. Art 50(2) marking for generative systems on the market before 2 Aug 2026: 2 Dec 2026. Unchanged: prohibitions and AI literacy (2 Feb 2025), GPAI duties (2 Aug 2025), Art 50 transparency (2 Aug 2026). New prohibitions from 2 Dec 2026. Opencontroller provides discovery, registry, policy-as-code mappings and rogue-agent handling as evidence for, not compliance with, the AI Act.

## Related

- [What does the EU AI Act require for AI agents, and when?](https://opencontroller.lyzr.com/blog/eu-ai-act-obligations-for-ai-agents.md)
- [What counts as a serious incident under the EU AI Act, and when must you report it?](https://opencontroller.lyzr.com/blog/eu-ai-act-serious-incident-reporting.md)
- [Do AI agents have to disclose they are AI under the EU AI Act?](https://opencontroller.lyzr.com/blog/do-ai-agents-need-to-disclose-they-are-ai-eu-ai-act.md)
- [More on Evidence and frameworks](https://opencontroller.lyzr.com/blog/cluster/evidence-and-frameworks)
