WhoIsCooking
Every developer I know has watched their fan spin up and wondered which of the half-dozen AI processes they left running is the culprit. WhoIsCooking answers that directly, naming the exact agent and giving you a way to cool it down. That's the kind of practical tooling the agent era is going to need more of.
The interesting part is what this says about how we work now. We've gone from running one IDE to running multiple agents that keep churning in the background, and nobody really tracks what they're doing to the machine. A utility like this makes the hidden cost of all that automation visible, which feels overdue.
I'd want to know how it detects the culprit, whether it's just reading the usual suspects or actually profiling CPU per process. And I wonder if this becomes a standard part of the stack or a niche fix. Either way, anything that keeps my Mac from sounding like a jet engine earns a look from me.
