Last updated: October 2026
The short answer: the dated changes coming to AI tools are regulatory, and the nearest ones are in December 2026, when providers of systems already on the market must meet the EU AI Act’s machine-readable marking rule and a new ninth prohibition, on AI that generates non-consensual sexual content, takes effect. High-risk obligations follow on 2 December 2027 and 2 August 2028, later than most articles still say. Everything else — agents, consolidation, open models — is forecasting, and this page keeps the two apart.
This article used to be a list of predictions. It has been rewritten, because predictions in this category are unfalsifiable, unaccountable and reliably wrong in the specifics, and because a page full of them is worth less than a page of dates you can actually plan against.
So it is now in two halves, kept strictly apart. The first is what is scheduled — obligations with dates attached, quoted from the source, which will land on the tools you use whether or not anybody's forecast comes true. The second is what is guesswork, labelled as guesswork, with no numbers attached to it.
Part One: What Is Actually on the Calendar
The most consequential fixed thing in the AI tooling landscape is the EU's AI Act, Regulation (EU) 2024/1689. Its dates are staggered, and — this is the part that makes most existing articles wrong — they were amended in July 2026 by Regulation (EU) 2026/1744.
The original Article 113 said the Regulation "shall apply from 2 August 2026", with prohibitions and the general provisions of Chapters I and II applying from 2 February 2025, the general-purpose AI and governance chapters from 2 August 2025, and — the line most widely quoted — "Article 6(1) and the corresponding obligations in this Regulation shall apply from 2 August 2027" for high-risk systems.
That last date has moved. Regulation (EU) 2026/1744, done at Strasbourg on 8 July 2026, amends Article 113 so that Chapter III high-risk obligations apply from:
(i) 2 December 2027 as regards AI systems classified as high-risk pursuant to Article 6(2) and Annex III; and (ii) 2 August 2028 as regards AI systems classified as high-risk pursuant to Article 6(1) and Annex I
The Commission's own summary of the framework says the same in plainer words: rules for systems used in certain high-risk areas will apply from 2 December 2027, and for systems integrated into products such as lifts or toys, from 2 August 2028. If you read an article that says high-risk obligations start on 2 August 2027, it was written before July 2026 and has not been updated. We were carrying a vaguer version of the same error on this page, and it is now corrected.
Two further dates are worth having in a calendar because they are close and they touch ordinary content work rather than only high-risk systems:
- 2 December 2026. The amended Article 111(4) requires that providers of AI systems generating synthetic audio, image, video or text content that were placed on the market before 2 August 2026 "shall take the necessary steps in order to comply with Article 50(2) by 2 December 2026". Article 50(2) is the machine-readable marking obligation.
- 27 July 2026. Articles 102 to 110 already apply, per the same amendment.
One more date was added by the same simplification package. The European Commission’s AI Act page, checked on 16 October 2026, now lists nine prohibited practices rather than eight. The ninth — “AI systems that generate non-consensual sexually explicit and intimate content or child sexual abuse (CSAM) material, such as AI ‘nudification’ apps” — was introduced by the AI Omnibus and, the Commission says, comes into effect in December 2026. The first eight have applied since February 2025.
Put together as a planning calendar, from the Commission’s page and the amended Regulation:
- 2 February 2025: prohibitions 1 to 8 and the AI literacy obligations apply.
- 2 August 2025: general-purpose AI and governance rules apply.
- 2 August 2026: the Regulation becomes generally applicable, including the transparency rules, with stated exceptions.
- December 2026: prohibition 9 takes effect; by 2 December 2026, providers of generative systems placed on the market before 2 August 2026 must meet the Article 50(2) marking duty.
- 2 December 2027: obligations for high-risk systems in the Annex III use cases.
- 2 August 2028: obligations for high-risk systems built into products covered by Annex I, such as lifts or toys.
The Official Journal quotations above were taken from the EU Publications Office texts and checked on 6 September 2026; the Commission page was rechecked on 16 October 2026. We note the check date deliberately: this is an area under active amendment, and a quotation without a date is a claim about a moving target.
What That Actually Changes for Someone Using These Tools
Two obligations sit in different places, and confusing them is the usual mistake.
On the tool makers. Article 50(2) requires providers of systems generating synthetic audio, image, video or text to ensure outputs are "marked in a machine-readable format and detectable as artificially generated or manipulated", with technical solutions that are "effective, interoperable, robust and reliable as far as this is technically feasible". The practical consequence for you is that provenance metadata is going to start appearing in files your tools produce, whether you asked for it or not, and it will survive some workflows and not others.
On the person publishing. Article 50(4) requires deployers to disclose deep-fake image, audio or video content as artificially generated or manipulated. For text, the second subparagraph is narrower and carries an exemption worth reading in full, because it describes exactly the arrangement a responsible publisher already runs: the disclosure duty applies to text "published with the purpose of informing the public on matters of public interest", and does not apply "where the AI-generated content has undergone a process of human review or editorial control and where a natural or legal person holds editorial responsibility for the publication of the content".
That is the legal frame; it is not legal advice, and whether and how it reaches you depends on where you and your audience are. Your own counsel is the source for that. But the direction is unambiguous, it applies to the EU market at scale, and the compliance burden lands on the vendors before it lands on you.
It also settles a long-running argument about disclosure norms in favour of the position this site already took: naming AI assistance and naming a human who is responsible for the output is not a confession, it is the exemption.
Part Two: What We Are Not Going to Predict
Here is the genre this article used to belong to, and why each item is being retired rather than updated.
- "Agents will do entire workflows by [date]." Possibly. The claim has been made with a specific date attached every year for several years, and the dates have passed. Autonomy is not one capability that arrives; it is a long tail of reliability improvements, and the last few percent of reliability is where the difficulty lives.
- "N platforms will consolidate the market." We previously printed a number here. We have deleted it, because we had no basis for it and neither does anyone else quoting one.
- "Pricing will move to pay-per-output." Some has, some has not, and vendors are experimenting in both directions at once. What is worth watching is not the direction but the unit, because that is what determines your bill: seats, messages, credits, minutes, documents, or a share of revenue.
- "Open models will capture X% of enterprise deployments." A real trend with no reliable public denominator. Any percentage you see is somebody's estimate presented as a measurement.
- Model version roadmaps. This is the fastest-moving part of the whole field and any article naming versions is stale within a quarter. Judge tools on what they do in your workflow this week.
Deleting a confident number and leaving nothing in its place reads as weaker writing. It is more honest writing, and in this category it is also more useful, because the reader who acted on our invented consolidation figure would have made a worse decision than the reader who acted on nothing.
Part Three: Decision-Proofing, Which Beats Forecasting
If you cannot know what changes, you can still make sure a change does not cost you much. This is the practical core of the article and it is entirely within your control.
- Keep the artefacts, not the access. A tool that produces documents, images or code you hold is a low-risk dependency at any quality level. A tool that becomes the only place a body of knowledge lives is a high-risk one even if it is excellent.
- Test the exit before you need it. Export during the trial, open the file, and ask whether you could rebuild from it. The same test we apply to website builders and their export functions applies to every subscription in the stack.
- Watch the pricing unit, not the price. Repricing in this category usually happens by changing what a credit buys rather than what a plan costs. A plan whose headline price is stable can still double in real cost. A dated example: GitHub announced that all Copilot plans would move to usage-based billing on 1 June 2026, replacing premium requests with AI credits consumed by token usage, while stating that “Base plan pricing is not changing.” Same price, different unit — and a heavy user’s real cost now depends on tokens rather than on a request count.
- Prefer tools that ground in your own data. Products built over sources you own — CustomGPT.ai is one shape of this, an agent over your own sitemap, PDFs or workspace that cites back to the source page — are less exposed to a model change than products whose value is the model itself.
- Keep a human accountable in writing. Beyond being good practice, the Article 50(4) exemption above is written in exactly those terms.
- Re-review adopted tools on a date. Our framework for choosing an AI tool sets out how to run that review so it ends in a decision rather than a renewal.
The One Prediction Worth Making
Only one, and it is safe because it is a statement about incentives rather than about technology: the gap between what these tools can do and what most organisations get out of them will keep widening. Capability is distributed evenly — anyone can buy the same subscription. The ability to specify a task precisely, judge whether the output is any good, and rebuild a process around it is not, and it is not improving at anything like the same rate.
Which means the scarce skill is not knowing which tool is best this month. It is being able to tell whether an output is right, in your own domain, quickly. That skill has appreciated every year of this cycle and there is no version of the next few years in which it depreciates.
Where agent marketplaces such as MuleRun are genuinely useful today is the narrow, repeatable end of that: tasks you can specify precisely and check quickly. The same framing tells you where they are not useful yet, which is anything you would struggle to write a specification for.
Where This Article Could Be Wrong
Two honest caveats, because a piece arguing against overconfident forecasting should not end on a flourish.
First, regulatory dates move. The July 2026 amendment above is the proof: a date that hundreds of articles had confidently printed for two years was changed. Ours could be superseded the same way, which is why the check date is stated and why the Official Journal rather than a summary is the source to return to.
Second, the case against this whole approach: refusing to forecast is comfortable, and there are decisions — hiring, a multi-year contract, a build-versus-buy call — where somebody has to take a view on where this goes, and "we do not know" is not an answer that helps them. Fair. Our position is that such a view should be taken explicitly, by a named person, on the record, with the reasoning attached — not absorbed from an article that assembled plausible-sounding numbers and never had to be right.
Disclosure: this article contains affiliate links. If you sign up through them we may earn a commission at no extra cost to you. It does not change what we recommend. Nothing here is legal advice; the regulatory material is quoted from the Official Journal and dated so you can check it yourself.
Frequently Asked Questions
When do the EU AI Act high-risk rules apply?
After the 2026 amendment, from 2 December 2027 for high-risk systems in the Annex III use cases and from 2 August 2028 for high-risk systems built into products covered by Annex I. The 2 August 2027 date still quoted in many articles has been replaced.
What changes for AI tools in December 2026?
Providers of generative AI systems placed on the market before 2 August 2026 must comply with the Article 50(2) machine-readable marking duty by 2 December 2026, and the Commission says the new ninth prohibition, on AI that generates non-consensual sexual content or child sexual abuse material, takes effect that month.
Do I have to label AI-written text I publish?
Under Article 50(4), the duty for text covers content published to inform the public on matters of public interest, and it does not apply where the content has undergone human review or editorial control and a person holds editorial responsibility. Whether the EU rules reach you depends on where you and your audience are.
Will AI tool prices go up?
Nobody can say reliably. What is observable is that vendors change the unit you pay in — GitHub moved Copilot to usage-based credits in June 2026 while keeping plan prices the same — so watch what a credit or request buys, not only the headline price.
Related Articles
