Control Modes
Control modes define how AgentOS connects to the target machine. There are two:- Host Mode — AgentOS runs directly on the target as software. It uses OS-level APIs for screenshots, input, and window management. This is the most common setup.
- Companion Mode — AgentOS runs on a separate device and controls the target through hardware (USB, Bluetooth, HDMI capture) or device bridges (ADB, IDB). No software installation on the target is needed.
Runtime Modes
Runtime modes define how AgentOS runs on the machine it’s installed on. There are two:- Standalone — AgentOS runs as a regular process in the user’s session. Install via
pip install askui-agent-os. Best for local development and testing. - OS Service — AgentOS runs as a Windows system service with SYSTEM privileges. Install via the Service Installer. Best for CI/CD, headless VMs, and enterprise deployments.
Capabilities
Capabilities are the building blocks your agents use — screenshots, keyboard input, mouse control, window management, process management, and more. What’s available depends on the combination of control mode and runtime mode:| Host Mode (Standalone) | Host Mode (OS Service) | Companion Mode | |
|---|---|---|---|
| Screenshots | Yes | Yes | Yes (HDMI capture) |
| Keyboard & mouse | Yes | Yes | Yes (USB/Bluetooth HID) |
| Window & process management | Yes | Yes | — |
| RDP resilience | — | Yes | — |
| Logon screen & CTRL+ALT+DEL | — | Yes | — |
| Mobile devices (ADB/IDB) | — | — | Yes |
How They Fit Together
Think of it as two independent choices:- Control mode — How do I reach the target? Software on the target (Host) or hardware from outside (Companion).
- Runtime mode — How does AgentOS run? As a regular process (Standalone) or as a system service (OS Service).
Control Modes
Host Mode vs Companion Mode.
Runtime Modes
Standalone vs OS Service.
Capabilities
Full capability matrix.