How It Works
AgentOS operates in two control modes:- Host Mode — AgentOS runs directly on the target machine as software. It controls the desktop via OS-level APIs with full access to screenshots, input, windows, and processes.
- Companion Mode — AgentOS runs on an external device (e.g. Raspberry Pi) and controls the target machine through hardware interfaces (USB, Bluetooth, HDMI capture). No software installation on the target required.
Why AgentOS?
Building a Computer Use Agent (CUA) proof-of-concept is straightforward — a few scripts with PyAutoGUI or xdotool and you have a demo running in minutes. But getting it to production is a different story. The gap between “works on my machine” and “runs reliably at scale” is where most teams get stuck. CI/CD integration is where it gets especially painful — VMs start at the logon screen, automation requires an interactive user session, and OS security restrictions block input injection from non-interactive processes. Solving this means dealing with session management, login automation, and privilege escalation before your agent can even begin its work. See our detailed comparisons for more:vs Automation Libraries
PyAutoGUI, RobotJS, xdotool, and why they fall short in production.
vs Remote Control Software
RDP, TeamViewer, VNC, RustDesk — built for humans, not agents.
What’s Next?
Quickstart
Get AgentOS running in under 5 minutes.
Control Modes
Host Mode vs Companion Mode — how AgentOS connects to targets.
Deployment
Find the right setup for your target.