horizon-device

# Horizon native VNC and device control Use this skill for Horizon VNC Device panels, simulators, and isolated native application tests. Browser pages use the `horizon-browser` skill and `browser_*` tools. Never drive a browser with device input. ## Native VNC Device panel Always observe interactive native tests live through a **Horizon native VNC Device panel in the user's current workspace**. Use a task-owned isolated desktop and private application state. Do not use noVNC or a browser viewer, or substitute screenshots or recordings for the live panel. Use the public `device_panel` MCP tool for viewer lifecycle. Call `operation: "list"` to discover panels in the caller's workspace. Create a task-owned viewer with `operation: "create"` and the fixture's numeric loopback `endpoint` (IP and nonzero port); retain its returned `panel_id`. This requires a Horizon-launched agent and a supporting host. The tool does not provision a desktop or forward input. The source checkout's `scripts/device-smoke/README.md` describes the isolated fixture; launch it with `--native-view` and use its `vnc_address`, not a browser URL. A VNC server on another machine's loopback is reached with optional `ssh` in create: `{ "host": "lab", "user": "deploy", "port": 2222 }` (user and port optional). `endpoint` is then the address as seen from that SSH host, typically `127.0.0.1:5900`. Horizon runs `ssh -W` with its own SSH configuration and keys, with strict host-key checking pinned regardless of `...