Claude Code can SSH into a remote machine and run a full hardware diagnostic - and most developers haven't tried this yet.
A developer who'd spent four years chasing unexplained PC performance problems gave Claude Code a single directive: analyze the machine for hardware bottlenecks, damage, and upgrade opportunities. The prompt specified what to check - RAM speeds, PCIe lane allocation, GPU utilization, monitor connections, event logs, and BIOS version. Claude Code SSHed from a Mac into the Windows machine, ran roughly 15 commands through PowerShell via WSL (Windows Subsystem for Linux - a compatibility layer that lets Linux-style commands run on Windows), and returned a detailed report flagging what was throttled or misconfigured.
No step-by-step instructions. One prompt, one structured report.
Claude Code has had computer-use and remote execution capabilities for a while. What's new is the realization that a well-structured diagnostic prompt can turn it into something closer to a hardware consultant than a coding tool. Most users still think of Claude Code as an autocomplete engine for writing and editing code. Give it SSH access and a clearly scoped objective, and the ceiling is considerably higher.
The practical requirement: SSH access needs to be configured between machines, and WSL must be installed on the Windows side. Neither step is complicated, but both require some initial setup. If that infrastructure is already in place, a diagnostic prompt like this can surface hardware problems that would otherwise take hours of manual research to identify.