It seems like it's driven either by 1) people hearing Macs are good for AI, buying one, and using Claude for inference, not realizing that you interact with the anthropic API from an internet connected hair dryer. Or 2) people want their agents to have blue bubbles.
I find it hard to believe that enough normal people are doing on device inference is driving Mac Mini's out of stock. And even if they were the Mac mini is not actually a very good platform for it.
Neo-Siri in iOS 27 removes the need for a lot of this, but before then, if you want to ask a robot about information that is stored in Apple notes, or to send an iMessage, a Mac mini is your only practical option.
It has nothing to do with Macs being especially good at AI. It has everything to do with being one of the last 'cheap' devices being sold with that much unified RAM.
The second is that the puck is heading towards local models. The people running their own 'Claws are usually experimenting running their own services either to save money or to explore the future where 95% of requests are handled on device.
You can sort of justify it by assuming it will last a long time and they’ll use it for other things, too.
OpenClaw supports all the mainstream (and free) chat apps like Discord, WhatsApp, Signal, Telegram... None of them requiring a MacOS machine.
Is it a lack of knowledge from the users or do they really value iMessage integration that much?
The relevant questions here are: will the person using this machine also conceivably be wearing a pair of $549 AirPod Max? Or a $399 base Apple Watch? Does that person expect to pay more or less for their largest-screen computing device than their headphones?
Framing that way points toward a $350 price point being a laptop for young children (younger than Apple Watch age, so lower elementary). That's a whole different software experience beyond just the hardware.
Anyone who wanted the OpenClaw use case that is comfortable with Linux probably already has several Linux machines (including a few Raspberry Pis) on-hand.
My understanding is that the barrier to entry to using iMessage makes iMessage a LOT more secure from spam. If you want to do mass iMessages you have to register as a business with Apple, go through all sorts of checks and attestations, etc.
At any rate, iMessages are a lot more trustworthy than SMS. So being able to spam people via iMessage is very desirable. I recall a few months ago a guy posting his little spam-iMessage-as-a-Service product here on HN. You could build your little iMessage spam army using a bunch of Mac Minis...
Unless you go for the very expensive options, most of the Mac Minis really aren't suitable for running local LLMs, they're painfully slow with prefill/processing input, and the models you are able to run don't handle long context very well, which these sort of long-running agents perform very differently with when you can.
I'll agree with your latter point, hard to beat the value of using something like OpenRouter or similar remote inference.
Even with local models, you can run the agent software and the inference workload on different hosts, which is what I'm doing at home. Beefy server responsible for inference, tiny VM on other server is running the actual agent software + RPC + bridges and what not.
I use Claude Pro ($20/m) as a glorified search engine (no ads/SEO) plus simple hobbyist dev things (shell scripts, managing my Mac, apps etc.
I also use it for tasks like - “search the web for top ten selling EVs, put them in a table” and then iterate - pivot tables, charts, additional research”. It could be cars, it could be broccoli. Code Work has facilities to streamline this type of work, but I usually drop into the CLI.
How much if any functionality would I need to recreate if I switch to OpenRouter and would be match my costs with the API approach. I don’t want any cost overruns. With Codex or Claude, if I run of tokens, no big deal, I can wait.
Thanks!