The anecdote at the heart of this is worth quoting exactly, because it's more specific than the claim built on top of it. Someone thought their Mac's performance problem was Chrome. It wasn't:

"So what I thought was a Chrome issue turned out to be one of the custom web applications that I had built was doing some really inefficient GPU usage. So I fixed that in like 10 minutes."

The claim being made is that an AI assistant can walk a non-developer through diagnosing and fixing a slow Mac — identifying which applications are misbehaving and suggesting lighter replacements. The general shape of that idea is real and available now: consumer AI assistants can already read screenshots, interpret Activity Monitor output, and answer questions like why is my fan running constantly. If your Mac is sluggish, describing the symptoms to an assistant and sharing what Activity Monitor shows is a reasonable first step that costs nothing and requires no expertise.

But an honest caveat is needed, because the quoted example is not actually a non-developer story. The fix in that quote involved a custom web application the speaker had built themselves — code they wrote, were able to diagnose at the GPU level, and were able to fix in ten minutes because it was theirs. That is a developer's win, and it's fine to say so plainly. A non-developer facing the same underlying problem — a web app hogging the GPU — would not be fixing its code. They'd be identifying the culprit and switching away from it, which is a more modest but still useful outcome.

So here's what the claim gets right and what it glosses over. What an assistant can genuinely do for a non-technical user today: translate confusing system signals into plain language, help you figure out which app is eating resources, and suggest alternatives — a lighter browser, a different email client, closing the app that only exists to sync files you rarely open. What it cannot do is fix the software itself. If the problem is a poorly written application, your options are to stop using it or live with it. And the assistant can't see your machine on its own — you have to feed it the information, which means it can only be as accurate as what you describe or show it.

There are also limits nobody should skip past. An assistant's suggestion to "just replace" an application assumes a replacement exists and that switching is free — neither is always true if the app is tied to your job. And assistant advice is only as good as the diagnosis; blaming the wrong process can send you on a wild goose chase of uninstalling things that weren't the problem.

Who is this for, then? Two audiences, honestly separated. Non-developers get real but bounded value: guided triage for a slow Mac, for free, at the level of find the greedy app and avoid it. Developers get the deeper version — as the ten-minute fix above shows — because when the culprit is their own code, an assistant can help find it and they can actually repair it.

It is usable today, not speculative. Just don't expect the ten-minute fix unless the broken thing is yours to fix.