AgentOS can run in two modes. Choose based on your use case.
Standalone
AgentOS runs as a regular process in the current user’s session.
Best for: Local development, interactive desktop use, and manual testing.
pip install askui-agent-os
That’s it — your agent code uses AgentOS automatically.
OS Service
AgentOS runs as a Windows system service with SYSTEM privileges.
Best for: Enterprise deployments, CI/CD pipelines, headless VMs, and scenarios where RDP sessions may disconnect.
The OS service requires the Windows installer. Once installed, the AskUI SDK automatically uses the service instead of standalone mode.
Feature Comparison
| Feature | Standalone | OS Service |
|---|
| Primary use | Local dev / desktop | Enterprise / CI/CD |
| CI/CD ready | No | Yes (unattended/headless) |
| RDP resilience | No (session locks on disconnect) | Yes (session transfer) |
| Logon screen control | No | Yes |
| Send CTRL+ALT+DEL | No | Yes (Secure Attention Sequence) |
| Privileges | Current user | SYSTEM |
| Install method | pip install | Windows installer |
Not sure which to pick? Start with standalone for development. Move to the OS service when you need CI/CD, headless VMs, or RDP resilience.