Skip to main content
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.

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.
Best for: Desktop automation, CI/CD pipelines, enterprise VMs.

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).
Best for: Locked-down environments, embedded systems, kiosks, mobile devices, and any target where you cannot install software.

Comparison

Host ModeCompanion Mode
Where AgentOS runsOn the target machineOn an external device
Connection to targetOS-level APIsHardware (USB, Bluetooth, HDMI) or device bridge (ADB/IDB)
Software on targetRequiredNot required
OS service supportYes (Windows)No
Platform supportWindows, macOS, LinuxAny device with USB/HDMI/Bluetooth; Android (ADB), iOS (IDB planned)
For a detailed breakdown of what each mode can do, see Capabilities.

What’s Next?

Capabilities

Full list of capabilities by control mode.

Deployment Scenarios

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.