Siri AI

It’s been challenging for me to think and write about Siri AI this summer, and I’ve already explained why: as a person whose workflow now revolves around agentic tools, I was not impressed by Siri AI at first.

I don’t think I was the only “power user” on Apple platforms who’s had this thought since getting their hands on the first beta of iOS 27 in June. If you’re reading this, chances are you’re pretty well versed in what models by OpenAI, Anthropic, or others now offer in terms of assistant features, web-based app integrations, memory, long-running tasks, and more. The product surface of Siri AI – the tentpole feature of iOS 27 that Apple is finally shipping after a two-year delay – has very little in common with those other agents or assistants, whatever you want to call them. Technically, yes – they are all based on a large language model under the hood. From a benchmark perspective, Apple’s new Foundation models are vastly behind the latest state of the AI frontier currently occupied by four American labs.

But as a product for people, Siri AI has a threefold advantage that no other company can match:

  1. It’s built right into your phone or computer
  2. It has a built-in knowledge graph about you in the form of personal context
  3. It can act upon, and retrieve data from, the native apps you use every day, from Apple to third-party ones

And these advantages sum up why I struggled to understand Siri AI at first. Is Siri AI only passable because it has an unfair advantage due to proprietary integrations that other AI models can’t use? Can it stand on its own as a good implementation of AI for most people? Does it fundamentally reinvent how we use our devices, or is it just a lot of hype for a slightly better Siri?

Unpacking the answers to these questions will be my goal with this chapter. But I’m going to do something unusual and share my takeaways up front, since they frame how I’ve been using and thinking about Siri AI.

I find Siri AI’s underlying models to be subpar compared to the competition: for anything beyond a simple knowledge query, I can’t see Siri AI replacing ChatGPT and its superior reasoning modes combined with web search. For simpler queries – the kind that a Google AI overview could also capably answer – the balance of speed and terse formatting is optimal in Siri AI. If I’m watching a movie and want to know how old an actor is, or if I want to know the meaning of a word, Siri AI is perfect for it and I no longer need to reach for ChatGPT or my personal agent in Open Minis. As we’ll see later, I find the Siri app to be extremely barebones and representative of the state of the art for chatbot design…two years ago.

The lack of an “agent mode” for Siri AI stings, and it’s why I can’t replace my beloved Codex or Hermes Agent setups with it.

However, Siri AI eventually clicked for me for the opposite reason: it can do things in and with apps that no other third-party agent can. Yes, they are simpler actions, and, no, results aren’t always perfect; but if you love the Apple app ecosystem and prefer using excellent native apps to cross-platform web ones, Siri AI is a breath of fresh air in the AI landscape right now.

See, Siri AI is complicated, polarizing, and almost impossible to agree upon.

Welcome to AI, Apple.

Foundation Models and Siri AI’s Architecture

Before I cover what the new Siri actually looks like and how it is split across a system-wide assistant and a brand new app, let’s talk about what it is and what powers it under the hood.

The new Siri is powered by a system orchestrator that coordinates user requests across different modalities (text, voice, and images) and five new Apple Foundation models, which are:

  • AFM 3 Core
  • AFM 3 Core Advanced
  • ADM 3 Cloud
  • AFM 3 Cloud
  • AFM 3 Cloud Pro

The first two are on-device models, with Core Advanced being exclusive to more recent devices with higher RAM. ADM Cloud is an image diffusion model that runs in the cloud, and which I will not cover in this review since I have no interest in generative images. AFM Cloud and Cloud Pro are cloud models running on Private Cloud Compute, with some differences: while Cloud is optimized for latency and efficiency (both for users, since it’s faster, and for Apple, since it costs less to serve), Cloud Pro is capable of deeper reasoning and agentic tool use, and it does not currently run on Apple-made servers. Instead, Apple teamed up with Google and NVIDIA to host Cloud Pro on NVIDIA GPUs running on Google Cloud, while maintaining the same privacy and security guarantees as “regular” PCC. (Only Apple can deploy software to these nodes, and only Apple can sign that software. More details here.)

All of these models were, according to Apple, trained with proprietary data and reinforcement learning, then “refined” with data from frontier Gemini models. Essentially, the new AFM family of models was refined with distilled Gemini outputs. I can’t stress this enough: although Siri AI and AFM may exhibit some behaviors reminiscent of Gemini (as I’ll explain later), Siri AI is not “powered by Gemini” and there is no Gemini to be found in Apple’s operating systems. No Gemini model or agentic harness is being used by Apple.

There are a couple more details worth exploring about the underlying nature of Siri AI. The first concerns what is, in my opinion, the most interesting model of the bunch – the new AFM 3 Core Advanced that runs on-device. For starters, Apple now has a larger local model that is multimodal: Core Advanced supports vision capabilities and powers the advanced dictation and expressive voices of the new Siri. Because of the increased footprint and technical requirements of this model, however, Apple had to restrict it to more modern devices:

  • iPhone Air, iPhone 17 Pro, iPhone 17 Pro Max, iPad (M4) or later with at least 12 GB of RAM
  • Mac (M3) or later with at least 12 GB of RAM
  • Apple Vision Pro with M5 (I always forget this exists)

The architecture of the model itself is also interesting. As I previously explained, while AFM 3 Core is still a 3B model with a dense architecture, AFM 3 Core Advanced is a 20B model that can run on devices with 12 GB of RAM. That’s made possible by a technology that Apple invented for sparse architecture models in which the model is stored in flash memory, activated parameters are locked in per prompt, and only 1 to 4 billion parameters are activated concurrently depending on the user’s request. From Apple:

One area of deep innovation is our most powerful on-device model, AFM 3 Core Advanced. Traditional large language models—whether dense or sparsely activated—require all weights to reside in active memory (DRAM), creating a massive footprint that limits scalability on consumer hardware. To break this barrier, AFM 3 Core Advanced introduces a novel sparsely activated architecture built on Instruction-Following Pruning (IFP), a technique developed by Apple researchers.
Instead of forcing the entire model into DRAM, the full model is stored in flash memory (NAND). Because NAND-to-DRAM bandwidth is too slow to swap weights token by token, as standard MoE models require, AFM 3 Core Advanced makes routing decisions per prompt. A lightweight, dense block selects a fixed set of experts during initial processing, periodically reselecting them during generation. To minimize data movement, the model relies on a high percentage of always-active “shared experts” alongside input-dependent “routed experts” swapped into DRAM only when needed.

You don’t need to be an AI expert to understand that what Apple wants to achieve here seems remarkably complex and optimistic. Here we have a company that is two years late to its original promises for an AI-powered Siri, and which is saying it has built a system to orchestrate five models, across multiple modalities, with support for proprietary World Knowledge (since you can now ask Siri general questions about anything, too), and which is going to draw from your personal context on-device as well as integrate with all kinds of third-party apps. And while all of this is happening, the system should know how to split inference across local and cloud models, how to allocate reasoning effort levels, how to coordinate actions across apps, and how to do it all in less than 15 seconds with a nice, minimalistic UI.

When I started working on this review, I struggled to visualize and understand the new Siri AI architecture in my head, so I built something with Fable 5.1 and GPT-6 Astra to help me, and I’m embedding it in this review because maybe it’ll help you too. For the following visualization, I started from Apple’s official Siri AI graphic that the company shared at WWDC, then I combined it with the Apple Intelligence Report that can be exported directly from the Settings app in iOS and iPadOS 27. The report contains all Siri AI requests that were issued by the user over the span of 7 or 30 days, and it includes details on the steps taken by Siri AI, what tools were loaded, how many tokens were in the system prompt, what third-party apps returned via App Intents, how much time each step took, and more.

The interactive visualization shows you some examples from my real requests – typos and everything – that were performed with Apple’s built-in apps as well as AskPlay and Emoji Countdown. As you can see, it’s a very intricate system that is executed remarkably fast by Siri AI and the system orchestrator.

Inside a Siri request

Siri is built in layers. Select a layer to see what it does. Then follow five real requests, one step at a time.

Five real requests

Each one was recorded on an iPhone running the iOS 27 beta. Three went to Siri. Two went from apps straight to Apple’s models. Pick one to follow it step by step.

Siri · iPhone · Aug 31, 2026

“Set a 75 minute timer”

The simplest case: one tool and one reply. The model calls started about a second apart. To set a timer, the model received a 111,030-character prompt. The request itself was 21 characters; most of the rest were instructions.

2 model calls1.1 s between first and last call starts111,030-character first promptPrivate Cloud Compute

  1. Your request

    “Set a 75 monite timer”

  2. 0.0 s
    Clock

    Start the timer

    The recorded request says “monite”. The model treated it as minutes and requested a 1 hour, 15 minute timer. The tool result reports a running timer in Clock.

    Details
    Model call 1 · Siri planner v5 · 0.000 s after the first call
    New in the conversation
    Device state: Monday 8:33 PM, iPhone, English, en-US, 12-hour time, Display+Voice
    Settings is the app in the foreground
    Live entity: a parked car from Maps, 20 m away
    Prompt
    111,030 characters · 32-token thinking budget
    102,194 instructions874 user turns + context1,043 earlier steps6,919 framing
    21 sections of instructions
    Siri Identity353
    Entities2,244
    Tools6,909
    Device State2,588
    Fixed Tools315
    App Span Match Tools514
    Structured Query Format search948
    Sources search19,406
    Search Purpose & Presentation2,812
    Filling Parameters search1,957
    When Multiple Matches Are Found search442
    Toolbox Catalog4,263
    Your Responses434
    Display+Voice mode response3,791
    Voice mode response1,029
    Formulating Your Response3,287
    Compose using these elements response13,869
    Responding response3,987
    Guardrails9,567
    Framework Directives586
    Platform Instructions22,893
    Decision
    create_and_start_timerPT75M
    Converts 75 minutes to the timer’s duration format.
    Arguments
    { "duration": "PT75M" }

    The next model prompt records this tool call and its result; the earlier response field alone does not show them.

    Result
    Timer running in Clock: 1 hour, 15 minutes, fires at 21:48:18
    Clock 1307 characters
    Recorded response
    Nothing. The response field is empty.
  3. +1.1 s
    Siri replies

    “I’ve set a timer for 1 hour and 15 minutes.”

    A Clock card with the running timer came back with the reply.

    Details
    Model call 2 · Siri planner v5 · 1.050 s after the first call
    New in the conversation
    The timer result: TimerEntity, Clock, state running
    Prompt
    111,406 characters · 32-token thinking budget
    102,194 instructions874 user turns + context1,355 earlier steps6,983 framing
    Decision
    I’ve set a timer for 1 hour and 15 minutes.
    Shows a card: Timer card · Clock · 1 citation
    Recorded response
    Readable text: 149 characters.

Siri · iPhone · Sep 5, 2026

“What’s 30% of this”

“This” arrived with Calculator screen context. The model supplied 8,985 to a calculation tool and returned the correct result. The report includes an image marker, but no viewable pixels to check the number it read.

2 model calls1.9 s between first and last call starts109,848-character first promptPrivate Cloud Compute

  1. Your request

    “What’s 30% of this”

  2. 0.0 s
    Calculation tool

    Calculate 30% of 8,985

    The prompt names Calculator as the focused app. The model asked a math tool for 30% of 8,985; the tool returned 2,695.5.

    Details
    Model call 1 · Siri planner v4 · 0.000 s after the first call
    New in the conversation
    The user asks “What’s 30% of this”.
    Device context names Calculator as the focused app and includes an image marker. The export does not contain viewable image pixels.
    Prompt
    109,848 characters · 50-token thinking budget
    99,756 instructions2,942 user turns + context1,093 earlier steps6,057 framing
    21 sections of instructions
    Siri Identity353
    Entities2,244
    Tools6,909
    Device State2,588
    Fixed Tools315
    App Span Match Tools514
    Structured Query Format search948
    Sources search19,406
    Search Purpose & Presentation2,812
    Filling Parameters search1,957
    When Multiple Matches Are Found search442
    Toolbox Catalog4,263
    Your Responses434
    Display+Voice mode response3,791
    Voice mode response1,029
    Formulating Your Response3,287
    Compose using these elements response13,869
    Responding response3,987
    Guardrails9,567
    Framework Directives586
    Platform Instructions20,455
    Decision
    math_calculation“30% of 8985”
    The next prompt records this call. The model used 8,985; the image marker alone cannot verify that this was the number on screen.
    Arguments
    { "query": "30% of 8985" }

    The next model prompt records this tool call and its result; the earlier response field alone does not show them.

    Result
    The calculation tool returned 2,695.5 for 30% of 8,985.
    312 characters
    Recorded response
    Only an unreadable thought signature: 194 bytes.
  3. +1.9 s
    Siri replies

    “30% of 8,985 is 2,695.5.”

    The answer matches the calculation. The reply also references a result card. The report does not establish what was visible in the image.

    Details
    Model call 2 · Siri planner v4 · 1.950 s after the first call
    New in the conversation
    The calculation result: numeric_result 2695.5.
    Prompt
    110,214 characters · 50-token thinking budget
    99,756 instructions2,942 user turns + context1,395 earlier steps6,121 framing
    Decision
    30% of 8,985 is 2,695.5.
    Shows a card: Calculation result card
    The recorded text matches the tool result. The report does not show the source image pixels.
    Recorded response
    An unreadable thought signature (167 bytes), then 152 characters of readable text.

Siri · iPhone · Aug 28, 2026

“Research a podcast guest and save a report in Notes”

Search results became material for an action. Siri searched, loaded a tool, wrote the note, and confirmed. About nine seconds separate the first and last model-call starts.

4 model calls9.1 s between first and last call starts113,500-character first promptPrivate Cloud Compute

  1. Your request

    “I am interviewing •••••••••• of ••••••••••• on my podcast NPC. Do a comprehensive research about him, his games, and everything. Have I ever interviewing him or covered his games before? What’s his background? What are their games about? Make it a comprehensive report with rich formatting and links and save it into Notes with NotesCTL.”

  2. 0.0 s
    Search

    Search the web and your apps

    One search asked for web results and personal content at once. It returned 26 web results and matches from six apps, including Notes and Mail.

    Details
    Model call 1 · Siri planner v4 · 0.000 s after the first call
    New in the conversation
    Device state: Friday 9:41 AM, iPhone, English, Display+Voice
    Span matches: “podcast”, “Notes” and “games” in the request matched the Podcasts, Notes and Games apps
    Live entity: a parked car from Maps, 7 m away
    Prompt
    113,500 characters · 50-token thinking budget
    104,673 instructions1,198 user turns + context1,150 earlier steps6,479 framing
    21 sections of instructions
    Siri Identity353
    Entities2,244
    Tools6,909
    Device State2,588
    Fixed Tools315
    App Span Match Tools514
    Structured Query Format search948
    Sources search19,406
    Search Purpose & Presentation2,812
    Filling Parameters search1,957
    When Multiple Matches Are Found search442
    Toolbox Catalog4,263
    Your Responses434
    Display+Voice mode response3,791
    Voice mode response1,029
    Formulating Your Response3,287
    Compose using these elements response13,869
    Responding response3,987
    Guardrails9,567
    Framework Directives586
    Platform Instructions25,372
    Decision
    find•••••••••• •••••••••••
    purpose: use_in_tool — the results are for the planner, not for showing the user.
    Arguments
    { "query": "•••••••••• •••••••••••", "purpose": "use_in_tool", "auto_present_results": false, "structured_query": { "web": [{ "query": "•••••••••• ••••••••••• background games" }], "generic": [ { "keywords": [ "••••••••••", "NPC", "podcast", "interview", "•••••••••••", "••••••••••", "••••••••••" ] } ] } }

    The next model prompt records this tool call and its result; the earlier response field alone does not show them.

    Result
    26 web results (10 passages shown, with entity images) plus matches from Music, Mail, Notes, Calendar, Reminders and Safari
    Web 10 of 26Music 9Mail 2 of 5Notes 6 of 9Calendar 5Reminders 5Safari 546,582 characters
    Recorded response
    Only an unreadable thought signature: 341 bytes.
  3. +4.3 s
    Load a tool

    Get the Notes tool

    Siri doesn’t start with every tool loaded. The model asked for the Notes tool, and its instructions were added to the next prompt.

    Details
    Model call 2 · Siri planner v4 · 4.319 s after the first call
    New in the conversation
    46,582 characters of web passages and local matches
    Prompt
    150,929 characters · 50-token thinking budget
    104,673 instructions1,198 user turns + context38,483 earlier steps6,575 framing
    Decision
    get_toolsmanage_note
    manage_note is listed in the Toolbox Catalog but not loaded; the planner asks for its full spec.
    Arguments
    { "tool_names": ["manage_note"] }

    The next model prompt records this tool call and its result; the earlier response field alone does not show them.

    Result
    Success — the tool spec is added to the next prompt
    76 characters
    Recorded response
    Only an unreadable thought signature: 196 bytes.
  4. +6.7 s
    Notes

    Create the note

    Notes saved a report of 954 characters with eight citations.

    Details
    Model call 3 · Siri planner v4 · 6.668 s after the first call
    New in the conversation
    The manage_note tool, now in the prompt
    Prompt
    153,699 characters · 50-token thinking budget
    106,782 instructions1,198 user turns + context38,584 earlier steps7,135 framing
    Platform Instructions: 27,481 characters, grew by 2,109 characters: the manage_note spec
    Decision
    manage_noteaction create
    The recorded tool call uses Siri’s manage_note tool. The note includes eight citation tags.
    Arguments
    { "action": "create", "app": "Notes", "content": "•••••••••• is the founder and creative director of •••••••••••⁠. […]", "contentChars": 954, "citations": 8, "name": "Research: •••••••••• (•••••••••••⁠)" }

    The next model prompt records this tool call and its result; the earlier response field alone does not show them.

    Result
    Note created in Notes, dated 2026-08-28
    Notes 12,192 characters
    Recorded response
    Only an unreadable thought signature: 283 bytes.
  5. +9.1 s
    Siri replies

    “I’ve compiled a comprehensive research report on •••••••••• and •••••••••••⁠, and saved it to your Notes. You have previously covered his game, *••••••••••*, on MacStories back in 2016, but this will be his first appearance on your podcast, NPC.”

    A card for the new note came back with the reply.

    Details
    Model call 4 · Siri planner v4 · 9.077 s after the first call
    New in the conversation
    The created note
    Prompt
    155,933 characters · 50-token thinking budget
    106,782 instructions1,198 user turns + context40,706 earlier steps7,247 framing
    Decision
    I’ve compiled a comprehensive research report on •••••••••• and •••••••••••⁠, and saved it to your Notes. You have previously covered his game, *••••••••••*, on MacStories back in 2016, but this will be his first appearance on your podcast, NPC.
    The visible response also includes cited background material.
    Shows a card: Research note card · Notes · 2 citations
    This confirmation is visible after a thought signature; the report does not show whether it was spoken aloud.
    Recorded response
    An unreadable thought signature (226 bytes), then 1,911 characters of readable text.

AskPlay · uses Apple’s models directly · iPhone · Aug 31, 2026

“Play the best Bloc Party B-sides”

Not Siri. AskPlay is a music app that talks to Apple’s server model directly, with its own instructions and its own tools. The report shows two attempts; two unrelated calls between them are left out.

6 model calls44.1 s between first and last call starts11,314-character first promptPrivate Cloud Compute

  1. Your request

    “Riproduci le migliori b-side dei Bloc Party”

    Asked in Italian: “Riproduci le migliori b-side dei Bloc Party”.

    Context supplied by the app

    The app included this context in its model request.

    {"current_request":"Riproduci le migliori b-side dei Bloc Party","recent_context":[]}
  2. 0.0 s
    Model

    Write a plan as text

    The model answered with a text plan instead of using the app’s tool. AskPlay rejected it.

    Details
    Model call 1 · Foundation Model · server · 0.000 s after the first call
    New in the conversation
    AskPlay’s 10,205-character system prompt
    The request as JSON: current_request plus an empty recent_context
    Prompt
    11,314 characters
    10,205 app prompt85 app input + schema0 earlier steps1,024 framing
    Decision
    { "actions": [ { "tool": "play_mix", "query": "Bloc Party b-side", "count": 20, "placement": "replace", "media_type": null, "playlist_name": null, … } ] }
    A plan written as prose JSON instead of a structured tool call. The JSON is visible after the thought signature in this same response.
    Recorded response
    An unreadable thought signature (510 bytes), then 340 characters of readable text.
  3. +6.0 s
    Model

    Try again

    AskPlay asked for the required tool-call format. The model returned another text plan. The report does not show a second rejection.

    Details
    Model call 2 · Foundation Model · server · 5.980 s after the first call
    New in the conversation
    From the app: “ROUTING POLICY REJECTION: This action-shaped request requires a structured music plan, not a prose response. Re-read the original request and return one corrected propose_music_plan call containing the complete ordered actions array. […] Do not apologize or explain the retry.”
    recent_context now carries the original request and the prose answer
    Prompt
    12,235 characters
    10,205 app prompt1,006 app input + schema0 earlier steps1,024 framing
    Decision
    { "actions": [ { "tool": "play_mix", "query": "Bloc Party b-sides", "count": 20, "placement": "replace", "media_type": null, "playlist_name": null, "rating": null, "shuffle": null, "songs": [], "seconds": null, "mode": null, "action": null } ] }
    The retry again returned visible prose JSON after a thought signature. A later request starts with fresh context; the export does not explain why.
    Recorded response
    An unreadable thought signature (1,851 bytes), then 341 characters of readable text.
  4. +37.1 s
    You

    “Same request, new attempt”

    The report doesn’t say whether the app or the person started it.

  5. +37.1 s
    AskPlay tool

    Use the app’s tool

    The new attempt added a 32-token thinking budget. This time the model called AskPlay’s tool with a 20-song plan. The app recorded it.

    Details
    Model call 3 · Foundation Model · server · 37.099 s after the first call
    New in the conversation
    The same request again, fresh context
    The system turn now carries a 32-token silent-thinking budget
    Prompt
    11,345 characters · 32-token thinking budget
    10,205 app prompt85 app input + schema0 earlier steps1,055 framing
    Decision
    propose_music_planplan play_mix “Bloc Party b-side” · count 20
    This time a real tool call.
    Arguments
    { "actions": [ { "tool": "play_mix", "query": "Bloc Party b-side", "count": 20, "media_type": "song", "placement": "replace" } ] }

    The next model prompt records this tool call and its result; the earlier response field alone does not show them.

    Result
    The app records the plan and stops the loop
    260 characters
    “AskPlay captured the proposed arguments. Do not call another tool.”
    Recorded response
    Nothing. The response field is empty.
  6. +37.8 s
    AskPlay replies

    “Riproduco una selezione delle migliori b-side dei Bloc Party.”

    “I’ll play a selection of the best Bloc Party B-sides.”

    Details
    Model call 4 · Foundation Model · server · 37.753 s after the first call
    New in the conversation
    The captured plan
    Prompt
    11,703 characters · 32-token thinking budget
    10,205 app prompt85 app input + schema246 earlier steps1,167 framing
    Decision
    Riproduco una selezione delle migliori b-side dei Bloc Party.
    Recorded response
    Readable text: 61 characters.
  7. +40.9 s
    AskPlay tool

    Expand the plan

    A second, much smaller prompt asked the model to turn the plan into 30 songs.

    Details
    Model call 5 · Foundation Model · server · 40.894 s after the first call
    New in the conversation
    A second, smaller system prompt (2,514 characters)
    Stage-two input: original_request, placement: replace, requested_playback_count: 20, required_candidate_count: 30, theme_query: “Bloc Party b-side”
    Prompt
    3,383 characters · 32-token thinking budget
    2,514 app prompt182 app input + schema0 earlier steps687 framing
    Decision
    propose_music_planplan play_mix “Bloc Party b-side” · count 30
    Expands the plan into 30 candidate songs.
    Arguments
    { "actions": [ { "tool": "play_mix", "query": "Bloc Party b-side", "count": 30, "placement": "replace", "songs": "30 titles" } ] }

    The next model prompt records this tool call and its result; the earlier response field alone does not show them.

    Result
    Captured
    1,444 characters
    “AskPlay captured the proposed arguments. Do not call another tool.”
    Recorded response
    Nothing. The response field is empty.
  8. +44.1 s
    Model

    Return 30 song titles

    AskPlay received the expanded plan. The report doesn’t show whether the songs existed or played.

    Details
    Model call 6 · Foundation Model · server · 44.093 s after the first call
    New in the conversation
    The captured 30-song plan
    Prompt
    4,925 characters · 32-token thinking budget
    2,514 app prompt182 app input + schema966 earlier steps1,263 framing
    Decision
    { "actions": [ { "tool": "play_mix", "count": 30, "placement": "replace", "query": "Bloc Party b-side", "songs": [ … 30 titles … ] } ] }
    The report records these proposed song titles. It does not show catalog validation or completed playback.
    30 songs
    1The Marshals
    2Always New Depths
    3Vision of You
    4Paper Planes
    5Letter from My Father
    6We Are Not Alone
    7Your Visits Are Getting Shorter
    8Retreat
    9The Answer
    10So Here We Are (B-⁠Side Version)
    11Tulips
    12Dry Ice
    13The Good News
    14B-⁠Side
    15Storm
    16Silent Alarm (B-⁠Side)
    17Diet
    18Version 2
    19Lullaby
    20Cloud
    21Nightmare
    22The Hunter
    23Heat
    24Neon
    25Echo
    26Crash
    27Wave
    28Pulse
    29Drift
    30Shift
    Recorded response
    Readable text: 1,239 characters.

Emoji Countdown · uses Apple’s models directly · iPhone · Sep 3, 2026

Pick calendar events worth counting down to

Emoji Countdown supplied 79 calendar events and rules to favor meaningful moments over routine meetings. One model call returned five suggestions, but renamed Thanksgiving as Veterans Day. Siri was not involved.

1 model callDuration not recorded6,049-character first promptPrivate Cloud Compute

  1. App prompt · excerpt

    “Choose the best countdowns among them and answer with the number of each event you choose.”

  2. 0.0 s
    Model

    Pick five events, misname one holiday

    The model selected a concert, two birthdays, and two holidays. Event 33 was Thanksgiving on November 26, but its returned title was “Veterans Day”. The report shows suggestions, not saved countdowns.

    Details
    Model call 1 · Foundation Model · server · 0.000 s after the first call
    New in the conversation
    Emoji Countdown’s own 1,078-character app prompt.
    79 numbered calendar events from the next twelve months, plus a structured output schema.
    The app asks for up to five meaningful events, ranked by importance rather than proximity. It asks for variety and excludes routine meetings.
    Prompt
    6,049 characters
    1,078 app prompt4,841 app input + schema0 earlier steps130 framing
    Decision
    { "suggestions": [ { "candidate": 19, "title": "•••••••••••••", "emoji": "🎤" }, { "candidate": 18, "title": "••••••••••••••", "emoji": "🎂" }, { "candidate": 33, "title": "Veterans Day", "emoji": "🎖️" }, { "candidate": 37, "title": "Christmas Eve", "emoji": "🎄" }, { "candidate": 67, "title": "••••••••••••••", "emoji": "🎂" } ] }
    The five candidate numbers exist in the input, but candidate 33 is Thanksgiving on November 26. The model incorrectly titled it Veterans Day. This is a suggestion response; the export does not show countdown creation or display.
    Recorded response
    Readable text: 343 characters.
About this data

The examples come from two Apple Intelligence Reports exported from an iPhone on the iOS 27 beta. The research-to-Notes example is from August 28; the other examples also appear in the newer report. Names and personal details are replaced before publication.

The reports don’t show every internal step, where an app’s tools ran, or why a model was chosen. Times measure model-call starts, not how long Siri took to answer. The rings describe capabilities, not a required sequence for every request.

Some recorded responses begin with an unreadable “thought signature” and continue with readable text. A later prompt can reveal a tool call hidden in the earlier response. The details distinguish these sources. An empty response is missing evidence, not proof of failure.

Layers from Apple’s Siri diagram. Examples and model shares from Apple Intelligence Reports.

By and large, what Apple has built works, and as a user of Apple devices and the new Siri AI, you will never see any of its underlying complexity.

The new Siri AI is far from perfect and objectively behind the state of frontier AI models, but it’s also doing things that no other company is, and I firmly believe it is going to be good enough for millions of people.

If you’re coming from any other AI product from OpenAI, Anthropic, Google, or the rest of the industry, you must reset your expectations in more ways than one when it comes to Siri AI.

First, unless you’ve been on the beta and have already let your device go through its new indexing process, you’ll probably have to wait a few days until you a) get access to Siri AI and b) can use it to its full extent. In order to work properly, Siri AI needs to build an index of your context and apps, and this process isn’t quick. You can speed up the indexing by keeping your phone on Wi-Fi and connected to a charger, but it’s not immediate. You can monitor its progress via a system message displayed in the Settings app; in my experience, while the initial indexing takes a while, subsequent updates to the index are much faster, if not downright immediate in some cases (such as downloading a new app and asking Siri AI questions about it).

Second, you should let go of a bunch of UI conventions you’ve probably grown accustomed to when using ChatGPT or Claude over the past two years. There are no model pickers, reasoning selectors, skills, @mentions of plugins, context windows, memories, “fast modes”, or usage resets in Siri AI. This new product embodies the quintessential “it just works” Apple mantra – sometimes to a fault. The new Siri looks and works like a more conversational Siri that also comes with a dedicated Siri chatbot app. There is nothing you can configure or tweak about it besides, well, using your devices with different apps.

There is a fascinating dichotomy occurring between the underlying complexity of Siri AI and the utter simplicity presented to users. Most frontier AI models and products wear their complexity on their sleeves, with different levers to pull and settings to tweak if you want to get the most out of them. Apple isn’t giving users this kind of customization (or responsibility?) yet, and I think it’s the correct choice to ease over two billion people into the uncomfortable world of AI.

Granola: The AI notepad for back-to-back days. Try for 3 months, for free, with code MACSTORIES.

A
A
Add Bookmark
DarkLightAutomatic

Use this link to save your spot in the review and return to it later.
You can add this as a bookmark or share it with friends.