Extensions: How Claude and ChatGPT Become Siri Backends
The Extensions system is what developers should actually focus on.
iOS 27 opens Siri, Writing Tools, and Image Playground to third-party AI providers through a new Extensions framework. Users install the Claude app (or ChatGPT, or the Gemini app), then go to Settings → Apple Intelligence → Extensions to designate it as the backend for any Apple Intelligence feature. The routing is transparent—same Siri interface, different model answering. No modal. No handoff indicator. The user talks to Siri; Claude responds.
This is structurally different from the existing ChatGPT integration, which was an explicit handoff: “I’m sending this to ChatGPT” plus a modal break. Extensions make the AI swap invisible to the user. They interact with Siri normally; the query routes to whichever provider they’ve configured.
Apple confirmed Anthropic (Claude), OpenAI (ChatGPT), and Google Gemini direct as launch Extensions partners. The API is open—any AI provider can build an Extension—but approval requires App Review and App Store distribution through an iOS app. xAI has not announced a Grok Extension at the time of this writing.
App Intents 2.0
For developers building apps—not AI providers—App Intents 2.0 is the more immediately actionable announcement.
App Intents is the framework that lets Siri call into your app: search your content, take actions, surface your app’s capabilities in Spotlight and Shortcuts. Version 2.0 adds three things that fix the main complaints about v1:
Streaming responses. Your app streams partial results back to Siri instead of waiting for a complete response. The current architecture requires a full result before Siri renders anything—jarring on tasks that take more than 2–3 seconds. Streaming changes perceived latency dramatically for search-heavy intents.
Richer entity types. Structured domain objects that Siri understands semantically. A “meeting” in your calendar app, a “track” in a music app, a “reservation” in a restaurant app—Siri can reason about the attributes of these objects rather than just matching string queries against them. The delta from v1 is that Siri moves from keyword matching to intent understanding over your app’s data model.
Conversational follow-ups. Multi-turn interactions within a single Siri invocation. Users can refine a task (“show only Tuesday meetings” after a broader search) without re-invoking Siri. This was technically possible in v1 with significant complexity; v2 makes it a first-class pattern with a clean API surface.
Code structure from the pre-release documentation:
// App Intents 2.0 — streaming response
struct SearchMeetingsIntent: AppIntent {
static var title: LocalizedStringResource = "Search Meetings"
@Parameter(title: "Query")
var query: String
func perform() async throws -> some StreamingIntentResult & ReturnsValue<[MeetingEntity]> {
return .streamingResult { continuation in
for await meeting in meetingService.streamSearch(query: query) {
continuation.yield(meeting)
}
}
}
}
Migration from v1 is additive. Existing App Intents keep working. You opt into streaming and richer entity types per-intent.
Privacy Architecture for Extensions
The Gemini deal raises the obvious question: does $1 billion per year to Google mean Google sees your Siri queries?
PCC uses cryptographic attestation. Before sending any query, your iPhone verifies that the software running on PCC nodes matches Apple’s published binaries. No surveillance layer can be inserted without breaking the attestation chain. Apple has published PCC source code for independent security researchers to audit—this is verifiable, not a trust-me statement.
Third-party Extensions (Claude, ChatGPT, Gemini-direct) work differently. When you route Siri to Claude via Extensions, queries go to Anthropic’s servers under Anthropic’s privacy policy—not Apple’s PCC. The Extensions settings screen will display which provider handles data for each feature, and Apple requires all Extension providers to comply with App Store privacy nutrition labels.
For enterprise deployments: Apple is not shipping MDM controls for Extensions at iOS 27 GA. IT admins cannot block users from installing Claude and routing Siri to it at launch. Apple has indicated MDM Extension policies are on the roadmap. Enterprises concerned about AI vendor approval or data residency should factor this into iOS 27 rollout timelines.
What’s Shipping and When
What Changes for Developers Building on Claude and ChatGPT APIs
Two concrete things change if your app runs on Claude or ChatGPT.
Extensions routing means users can get your AI provider’s responses through native iOS features without opening your app. Writing Tools in any app, Siri queries, Image Playground—all routed to Claude if the user has configured it as their default. That’s distribution expansion through iOS’s own surface area, with zero marketing spend from your side.
The constraint: Extension routing strips your session context. Claude via Extensions receives the current query and Apple’s context payload—not your app’s conversation history or user preferences. For AI apps where session continuity drives quality (think therapy apps, long-running coding sessions, multi-step financial planning), the Extensions model doesn’t fit. Extensions are for stateless or single-query AI use cases.
App Intents 2.0 combined with Extensions creates an interesting pattern. If your app exposes domain entities through App Intents 2.0 and the user has Claude as their Extensions default, Siri calls your intent using Claude’s reasoning. A travel app surfacing flight entities gets Claude-powered Siri answering “what’s my gate for next Tuesday?” with actual contextual reasoning over your data model—not just a lookup. This is the highest-leverage path for most app developers: build the entity types, let Claude do the reasoning.
Developer Checklist Before September
- Verify Apple Developer Program enrollment — Extensions development and distribution requires it ($99/year). If you’re not enrolled, start the process now; approval can take days.
- Install iOS 27 developer beta 1 on a test device after the keynote today. The Extensions API and App Intents 2.0 documentation drops with the beta—don’t wait for WWDC session recordings.
- Audit your existing App Intents for streaming response candidates. Any intent with a response time over 2 seconds is a candidate. List entity types that could be richer.
- If you’re building on Claude or ChatGPT APIs, decide by June 30 whether an Extensions integration makes sense. App Review for new Extension capability has a first-mover queue—early approvals appear higher in Extension search results.
- Enterprise apps: brief your legal and compliance team now. iOS 27 ships without MDM Extension controls at GA, which means employees can route Siri queries to non-approved AI vendors from day one.
Full documentation will be at developer.apple.com following the June 8 keynote. WWDC sessions on App Intents 2.0 and the Extensions framework are expected to post within 48 hours. Both are recorded.
For cost modeling across Claude, GPT, and Gemini in your iOS app workloads, the WOWHOW AI API cost calculator covers Gemini 3.5 Flash and Anthropic Claude Sonnet 4.6 pricing. The developer tools collection includes starter kits for iOS AI app patterns and App Intents integration.
People Also Ask
What is the Apple Siri Extensions system in iOS 27?
Extensions is a framework in iOS 27 that lets users choose a third-party AI provider—Claude, ChatGPT, or Google Gemini—as the backend for Apple Intelligence features including Siri, Writing Tools, and Image Playground. The provider is configurable per-feature in Settings → Apple Intelligence → Extensions. The routing is transparent: same Siri interface, different model answering.
Does the Apple–Google Gemini deal mean Google can see your Siri queries?
No. Apple’s custom Gemini model runs on Apple’s Private Cloud Compute (PCC) infrastructure, not Google’s servers. PCC uses cryptographic attestation to verify Apple’s published software runs on the hardware nodes—query content is inaccessible to Google or Apple operators. Third-party Extensions (Claude, ChatGPT) do route queries to those providers’ servers under their own privacy policies.
When does iOS 27 ship and which iPhones support it?
iOS 27 is expected in September 2026 alongside the iPhone 17. Supported: iPhone 12 and newer. iPhone 11 and earlier are dropped from iOS 27 support.
What is App Intents 2.0?
App Intents 2.0 is the updated framework for letting Siri call into your app, announced at WWDC 2026. Key additions: streaming responses (partial results returned before completion), richer entity types (Siri understands your app’s domain objects semantically), and conversational follow-ups (multi-turn within one Siri invocation). Migration from v1 is additive—no breaking changes.
Can any AI provider build an iOS 27 Extension?
Yes. The Extensions API is open to any AI provider. Building an Extension requires an iOS app in the App Store, Apple Developer Program membership, and App Review approval for the Extension capability. Apple confirmed Anthropic, OpenAI, and Google as launch partners; other providers can submit extensions through the standard App Review process.
Comments · 0
Beta: comments are stored locally on your device and not visible to other readers.
No comments yet. Be the first to share your thoughts.