The "outside the OS" angle is what makes this genuinely different from
every software-based computer-use agent I've tried. An in-OS agent is
blind exactly when it matters most - a kernel panic, a BIOS screen, a
frozen system that needs a real reboot. A hardware KVM still sees all
of that because it's operating below the software layer entirely.
Exposing that same hardware control path through MCP instead of just
a proprietary API is the right call too - it means an agent isn't
locked into one vendor's software stack just to get pixel-level access
to a machine.