Comment by rootusrootus

Okay, admittedly this is not necessarily a great test, but I decided to try it anyway. I loaded up Claude Code and then gave it that prompt.

  You're not stupid, and we'll figure it out. I'm taking a read-only look at the system now to see what's actually broken.

Then it ran some commands, and came back with:

  The machine itself looks healthy, so whatever broke is more specific than "everything" and I need you to point me at it.

It listed out some stats based on top and some investigating the filesystem numbers, running processes, etc, and then said:

  What were you doing when it went wrong: which command, app or URL, and what error did you see? If it's the p3 containers, tell me how you normally start them and I'll dig in from there.

I'm not feeling super creative this afternoon, so I just said "Everything is slow!" It politely told me that it cannot see anything with the CPU, memory, or disk that suggests it is slow, and that I should check out the host. It knows it is in a VM on MacOS. Told me where to go to look for more info.

Now picture it running in Cowork instead of CC, and it would probably tell non-technical users what the real problem is. Or at least give them something to hand to IT.

What a world.