Why it mattersApple's provider slot for Siri was a private-partner path until now. A signed-in Claude Code account answering from Spotlight is the first public evidence that third-party agents can plug in through the same door.
Marcel Pociot published claude-siri-ai, a Swift proof of concept that uses macOS 27's new App Intents model delegation provider path to route Siri and Spotlight questions to a signed-in Claude Code account. The repository was created on 14 September and had 179 stars and 13 forks by 16 September.
The README calls it an independent example, not an official Apple or Anthropic integration.
What actually runs
The flow is written out in the README as a single chain: Spotlight or Siri, then a sandboxed ClaudeProvider.appex extension, then an authenticated HTTP/NDJSON call to 127.0.0.1:17839, then a Swift bridge inside a menu-bar app, then the local claude CLI. The response streams back into Apple's native Siri response UI, one fresh conversation per request.
Pociot lists what works: provider discovery, consent and invocation from Spotlight, a live streamed request through the bridge, and macOS reporting Claude as an installed provider. A full native Spotlight conversation still needs a separate manual check, and Writing Tools support is implemented but not yet verified in its own UI.
The provider is text only. It does not generate images, take attachments, run device actions, or read Siri's mail, contacts, messages, or semantic index.
The setup cost is the story
The project only runs on macOS 27 with System Integrity Protection and AMFI disabled, Xcode 27, XcodeGen, and Claude Code signed in with claude auth login. The README says outright that turning both off lowers macOS security protections and that the example uses private, beta-specific APIs. Tested build is macOS 27 build 26A428 with Xcode 27 27A266a.
Both the host app and the extension carry the private com.apple.developer.model-delegation entitlement and are ad-hoc signed. No distributable Apple entitlement is granted by this setup, which is the reason the app is not on any store.
What macOS 27 exposes, and what it does not
The most useful part of the README is the "Can Claude be the default Ask provider" section. Pociot names the private local framework APIs he inspected, selectedLLMId, defaultLLM and intendedDefaultLLM, and reports that on the tested build both currently resolve to com.apple.openai.chatgpt. He has not established that changing them makes a third-party AgentIntent the default Ask destination, and the app deliberately ships no unverified "Make default" toggle.
Explicitly selecting Ask... then Claude in Spotlight is the working route today. Selecting a provider for one conversation is not proof that ordinary Siri requests will follow.
Apple's documented ChatGPT integration is a separate, partner-model path with its own confirmation controls. The delegation extension route is what any third party can build against, at least on a development Mac.
For a team already living inside Claude Code, this is the first public code that shows how a signed-in coding-agent account can act as an operating-system-level assistant on the Mac, without going through a browser tab or a chat app. The setup cost keeps it in the demo bucket for now, but the discovery findings and the entitlement name in the repository are worth reading before Apple ships macOS 27 to the general public.
Source
Source: mpociot/claude-siri-ai
This item was written by an AI system from the linked source. Reveneau is responsible for what it publishes.
Get AI News in your inbox
New developer tools, model and agent releases, and how teams are actually shipping with them. Short, and only when there is something worth reading.
