If Siri Lets You Pick an AI, Read Beyond the Model Name

Key takeaways

• Letting an outside AI handle specific Siri requests would differ from replacing Siri’s core model.
• References in unreleased code would not establish that a feature will ship.
• Choosing a model should come with separate controls over what information it receives.
• Disconnecting a service and deleting information already shared require distinct controls.

Imagine Siri offering a choice between Claude and ChatGPT. If that option arrives in iOS 27, the obvious question will be which gives better answers. The less obvious question deserves equal billing: how much of your digital life would each service get to see?

What would you actually be choosing?

An AI picker could represent two very different arrangements.

In one, Siri hands particular requests to an outside service. Your chosen AI drafts an email; Siri sets the alarm. The external model handles a defined part of the job.

In the other, the outside model takes over more of the underlying work: interpreting what you mean and deciding what should happen next. That would put it much closer to the center of Siri’s operation.

Both arrangements could fit behind the same tidy settings menu. Their information needs could be quite different.

The useful distinction is task handoff versus core model replacement. Before comparing model names, users would need to know which responsibilities they were assigning—and what access those responsibilities require.

Code references have limits

Suppose Claude or ChatGPT appeared in unreleased code. That could suggest work on connecting multiple models. It would not, by itself, establish that users could choose between them.

A reference might belong to an internal experiment or something abandoned during development. Even a working selection screen would leave the shipping decision unresolved. Software development produces plenty of things that never make it into a release.

Any claim based on code needs three separate checks: whether the code is authentic, whether the feature works, and whether its release is confirmed.

Attaching “iOS 27” to the claim would not collapse those distinctions. Nor would evidence of an external model connection establish that Apple planned to let it run all of Siri.

The important setting is what leaves your device

Consider a simple request: “Find the time of my next meeting in my email.”

One possible design would extract the relevant details on the device and send only those details to an outside AI. Another would send the email body for the service to interpret.

The spoken answer could be identical. The information disclosed would not be.

A useful selection screen would make three things clear:

• Which service will process the request.
• Which messages, attachments, or other information it will receive.
• How long it will retain that information and what it will use it for.

That does not have to mean a wall of fine print before every request. Users could set boundaries once, with an additional prompt when a task needs information beyond those boundaries.

The principle is separate consent for data sharing. Liking a model’s writing style does not mean agreeing to send it every piece of context Siri can access.

Switching needs an exit plan

The real test of choice comes when you change your mind.

If you switch providers, when does the previous service stop receiving information? What happens to conversations and files it already holds? Should the new provider receive any previous conversation context?

Those are separate decisions. A single “Disconnect” button cannot explain them all.

In particular, disconnecting and deleting data need distinct explanations and controls. Stopping future transfers does not tell users what happens to information already sent.

Choice should also fit the task. Someone might want an outside AI for writing while keeping personal scheduling requests out of that service. One default model for everything would not capture that preference.

If Siri eventually offers an AI picker, the number of available models will tell only part of the story. The better test will be whether users can understand what they are sharing, limit it, and withdraw that permission. Choosing who answers should also mean choosing what they get to know.