The problem is that when using Apple Intelligence as a user, you never know when the OS will send your query to Apple Private Cloud instead of processing it with an on-device model. As far as I can tell, there is no way to keep Apple Intelligence enabled and at the same time disable automatically routing requests to APC if the OS deems the query is too complex to be processes locally. There simply isn't a single warning pop-up before your request gets sent to APC.
Thanks, that's an interesting observation! When I double-clicked on the "Siri" process in Activity Monitor, I saw that it's an app called "Siri AI".
If the "Siri AI" app has replaced Spotlight, then I wonder if Apple keeps building "personal context" despite Siri and Apple Intelligence being disabled.
It for sure doesn't sound well to disable Siri and still see a "Siri" process.
Thanks, I believe this is what the debloat script mentioned in my post does. I manually executed the `launchctl bootout` and `launchctl disable` commands on all Siri and AI-related services in the https://github.com/OleksandrKrupko/mac-os-debloat/blob/main/... script, but the "Siri" process ("Siri AI.app") still keeps running even after restarting.
The Siri AI.app is read-only, so I could not even remove it. But perhaps it would be possible to boot into Recovery, mount the system partition as rw and delete the Siri AI.app from the filesystem?
P.S. I did also disable mediaanalysisd and photoanalysisd, and those are NOT running. However, the Siri AI.app does keep running...
Yes, I did something similar: prior to disabling Siri, I set Siri's language to French and kept the system language set to English (UK), but the Siri AI.app ("Siri" process in Activity Monitor) just keeps running despite Siri being indicated as disabled in Settings.
If you are on macOS 27, could you please open Activity Monitor, search (filter) for "siri" and see if a process called "Siri" is still running?
You are right. The UI shows Siri disabled and offers to turn it on, but the process is still running. That process seems to change its name based on whether the UI thinks Siri is enabled; it can be called either just "Siri" or "Siri AI" but it’s the same executable.
FWIW it's entirely possible (and not uncommon) for a single executable to behave differently depending on the name it was launched under.
I have no idea in this case, but it's possible that "Siri" and "Siri AI" are genuinely different in behaviours and interfaces and dependencies, even if they are the same binary.
Same here. Unfortunately, if you use Xcode to develop for iOS, then Apple basically forces you to install macOS 27 to be able to develop for the new iPhones. The iPhone 18 Pro requires Xcode 27, and Xcode 27 won't run on Sequoia.
If anyone knows how to make the iPhone 18 Pro work with Xcode 26 on Sequoia, and in turn with iOS 27, I (and I'm sure many other people) would be very happy to hear how!
But it is possible to run even the latest Xcode 26.6 by directly executing Xcode.app/Contents/MacOS/Xcode, and Xcode will run. This trick doesn't work with Xcode 27 anymore though. If you try that, you'll see a warning message that says something like "Xcode requires macOS 26 to run".
It's a joke. Microsoft has been ignoring user preferences and doing what is good for Microsoft for many years now, and the parent poster was implying that Apple is now doing the same kind of bad behavior.
I think the people who aren't greeted by this dichotomy when turning their PC aren't catching the reference.
At the risk of explaining a joke: Windows tries to get you to set up things like OneDrive on startup with a "do it now" or "remind me later", there's no "never ask me about this again".