AgentOS operates in two control modes that determine how it connects to and controls a target machine. Both modes expose the same core concepts (screenshots, input, automation) — but the connection method differs.Documentation Index
Fetch the complete documentation index at: https://docs.askui.com/llms.txt
Use this file to discover all available pages before exploring further.
Host Mode
AgentOS runs directly on the target machine as software. It controls the desktop via OS-level APIs.- Agent code and AgentOS run on the same machine (or connect over the network).
- Full access to OS-level features: window management, process control, multi-display support.
- Can run as a Windows service for SYSTEM privileges, RDP resilience, and logon screen control.
- Supports Windows, macOS, and Linux.
Companion Mode
AgentOS runs on an external device and controls the target through hardware interfaces. No software needs to be installed on the target.- Input is sent via USB or Bluetooth HID (keyboard and mouse emulation).
- Screen capture happens via HDMI-to-USB capture devices.
- Mobile devices are controlled via ADB (Android) or IDB (iOS, planned).
Comparison
| Host Mode | Companion Mode | |
|---|---|---|
| Where AgentOS runs | On the target machine | On an external device |
| Connection to target | OS-level APIs | Hardware (USB, Bluetooth, HDMI) or device bridge (ADB/IDB) |
| Software on target | Required | Not required |
| OS service support | Yes (Windows) | No |
| Platform support | Windows, macOS, Linux | Any device with USB/HDMI/Bluetooth; Android (ADB), iOS (IDB planned) |
What’s Next?
Capabilities
Full list of capabilities by control mode.
Deployment
Find the right setup for your target.
Runtime Modes
Standalone vs OS service — choose the right runtime.
Install as Service
Set up AgentOS as a Windows service for CI/CD and enterprise.