AI Assistants Want OS Privileges

The Short Version

The AI assistant war is becoming an operating-system fight.

Not someday.

Now.

On July 16, the European Commission adopted legally binding measures under the Digital Markets Act that tell Google how it must open parts of Android and Google Search to rivals. One part covers Android interoperability for AI assistants. The other covers access to ranking, query, click, and view data from Google Search.

That sounds like Brussels paperwork.

It is actually a product map.

The Commission says Android is used by more than 60% of mobile users in the EU. It says third-party AI services need access to Android features such as voice commands, actions across apps, live translation, speech-to-text, reply suggestions, and contextual information like a recently visited place.

In plain English:

If Gemini can live deep inside Android, rivals should not be stuck at app level forever.

That is the story.

AI assistants are not just chatbots with nicer voices. To be useful, they need operating-system privileges: wake words, notifications, app intents, local files, screen context, browser state, calendars, messages, maps, payments, and a way to act across the phone without feeling like a web page trapped in a rectangle.

The model matters.

The OS decides what the model can touch.

And once the assistant can touch things, the platform owner suddenly has enormous power.

Very normal future. The default assistant setting is now industrial policy.

What Europe is actually forcing

The Commission is not saying "make Android open, vibes-wise."

It is specifying categories of access.

For Android, Google must give third-party AI service providers effective interoperability with key Android features. The Commission's Q&A says the measures cover eleven features, including voice commands, actions within and across apps, live translation, speech-to-text, and contextual suggestions.

Those are not decorative features.

They are the difference between:

"Open this app and ask the chatbot."

And:

"Hey assistant, answer this message, book the ride, translate the call, summarize what I am looking at, and do the next step in the app I already have open."

That second version is the product people actually want.

The Search side matters too. The Commission says Google must give eligible search services, including AI chatbots, access to certain ranking, query, click, and view data. The idea is to let rivals improve their own search and AI-search products without needing to recreate Google's behavioral data advantage from scratch.

That is a big deal.

Search data is not just an old internet asset.

It is training signal, ranking signal, intent signal, freshness signal, and product-distribution signal. In an AI assistant world, search becomes less like a page of links and more like a task substrate. The assistant needs to know what people ask, what they click, what they ignore, and which answers actually help.

No wonder Google is unhappy.

Google's response argues that the decisions risk privacy, security, and product quality. It says forced data sharing and interoperability can expose users to new risks and weaken safeguards.

Some of that is self-interested.

Some of it is also true.

Opening agent-level access to a phone is not like opening a weather API.

It is closer to deciding who gets keys to the building.

The assistant is not an app anymore

This is the mental shift.

Most AI companies still talk like the assistant is a destination.

Open ChatGPT.

Open Claude.

Open Gemini.

Ask the thing.

That is useful, but it is not the endgame.

The endgame is the assistant as a layer over the user's digital life.

That means the assistant has to operate where the user already is. It needs to understand the message on screen, the page in the browser, the meeting on the calendar, the route in Maps, the photo the user just took, the app that is currently active, the file the user is editing, and the notification that arrived thirty seconds ago.

An app can ask for permissions.

An operating system can orchestrate context.

That is why Google and Apple have an advantage.

Gemini can become part of Android. Siri can become part of iOS. Microsoft can push Copilot through Windows. Google can connect Gemini to Search, Chrome, Android, Gmail, Docs, Maps, and YouTube. Apple can connect Siri to local device context, privacy controls, sensors, and app intents.

A rival assistant can be smarter and still feel worse if it cannot reach the right surface at the right time.

That is the uncomfortable product truth.

Model quality gets you into the conversation.

OS access lets you do the job.

Apple is the shadow story

The Google ruling lands at an awkward moment because Apple has been saying a similar thing from the other side.

Apple says some of its new Siri AI features will not initially launch in the EU because of DMA concerns. The company has argued that the law's interoperability requirements could force it to compromise privacy and security.

Again, there is strategy in that answer.

Apple does not want regulators telling it how to expose deep iOS capabilities.

But the tension is real.

An assistant that can read your screen, take actions in apps, understand personal context, and move across services is powerful because it is intimate. The same access that makes the assistant useful also makes it dangerous if the wrong actor gets it, if permissions are unclear, if logs are weak, or if the model follows the wrong instruction.

That is exactly why yesterday's GPT-Red story matters, but from a different angle.

Yesterday was about testing agents before the internet attacks them.

Today is about where those agents are allowed to live.

The deeper the assistant goes into the OS, the more the security model becomes the product.

Europe is effectively saying:

"You cannot reserve the useful hooks for your own assistant forever."

Google and Apple are effectively saying:

"If you force those hooks open, you had better accept the security consequences."

Both sides have a point.

Annoying, but true.

This is not just about Google Search

It is tempting to treat the Search-data part as an old antitrust fight with AI seasoning.

That misses the shift.

Search data is becoming assistant fuel.

If an AI assistant is going to answer questions, recommend actions, compare products, summarize current events, route users to services, and maybe complete tasks directly, then search is no longer just a results page.

Search becomes one of the assistant's senses.

Google's advantage is not only that it has a search engine. It has decades of query behavior, ranking feedback, freshness signals, spam knowledge, local intent, shopping patterns, and the muscle memory of users asking Google first.

AI search rivals want that signal.

Regulators see that signal as a moat.

Google sees that signal as its product, its privacy obligation, and its competitive edge.

All three can be true.

The hard part is that "share search data" sounds simple until you ask:

• Which data?
• How fresh?
• At what granularity?
• With what anonymization?
• For which competitors?
• Under what security rules?
• Can the data be used to train models?
• Can Google protect users from re-identification?
• Can rivals build anything meaningful if the data is too aggregated?

This is not a clean open-data story.

It is the messy beginning of AI-search infrastructure regulation.

Very relaxing.

The platform owner has the easiest agent

The simplest way to understand the fight is this:

The best AI assistant is probably the one closest to the user's real context.

That creates a platform-owner problem.

If Google controls Android, Google can make Gemini feel native. If Apple controls iOS, Apple can make Siri feel native. If Microsoft controls Windows, Microsoft can make Copilot feel native. Everyone else has to ask permission.

That permission can be technical.

It can be commercial.

It can be buried in APIs.

It can be shaped by privacy rules, app-store review, background-execution limits, browser defaults, notification policies, file access, local model APIs, voice invocation, and a thousand small decisions that never look like "AI competition" until the assistant cannot do the thing.

This is where regulation becomes product design.

The DMA is not training a model.

It is deciding which model gets to stand near the user's digital nervous system.

That is why this story matters more than a normal platform fight.

If agents become the interface, platform defaults become agent defaults.

And agent defaults are going to be extremely valuable.

What builders should take from this

If you are building an assistant, do not think only in terms of model capability.

Think in terms of reachable surfaces.

Can your assistant be invoked at the right moment?

Can it see the right context?

Can it act in the right app?

Can it explain which permission it needs?

Can it operate without asking for the entire phone?

Can the user revoke access cleanly?

Can another app trust its action?

Can a regulator understand the control?

Those questions are now part of the product.

If you are a platform owner, the lesson is harsher:

Your AI assistant APIs are not just developer features.

They are competition policy, security architecture, and distribution strategy at the same time.

That is an awful combination.

It is also the real job.

The next assistant war will not be won only by the model that answers best in a blank chat.

It will be won by the system that can safely stand closest to the user's real life.

Europe just reminded Google that "closest" is not supposed to mean "only ours."

The rest of the industry should pay attention.

The AI assistant is becoming the operating system's most important guest.

And guests, apparently, now require regulatory architecture.