Use Windows VM Computer Use

Operate the VM-local computer-use backend, not the SSH terminal, hypervisor input, or host desktop. Keep orchestration over SSH and run the GUI agent in the active Windows user's interactive session.

Establish the Boundary

1. Confirm the intended VM, user, and target application before changing state.
2. Treat SSH as orchestration only. Windows OpenSSH normally runs commands in session 0, which cannot reliably access the logged-in desktop.
3. Do not use QMP, SPICE, RDP automation, host mouse injection, PowerShell UI Automation, or keyboard scripting as evidence that VM-local computer-use works. Use them only when the user explicitly requests that different control path.
4. Keep the requested GUI action narrow and harmless. Do not dismiss consequential dialogs, change settings, or save data without authorization.

Verify the VM Runtime