Runtime Modes
Standalone vs OS Service, choose the right AgentOS runtime mode.
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.
AgentOS is installed via the AskUI installer. A dedicated standalone installer (without AskUI Desktop) is coming soon.
Standalone installer coming soon
For now, standalone AgentOS is installed as part of the AskUI Desktop installer. A separate standalone installer is in progress.
Once installed, AskUI Desktop and the CLI use the local AgentOS instance 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, AskUI Desktop and the CLI automatically use the service instead of standalone mode.
Feature Comparison
| Feature | Standalone | OS Service |
|---|---|---|
| Primary use | Local dev / desktop | Enterprise / CI/CD |
| CI/CD ready (Windows) | No (requires OS service) | Yes (unattended/headless) |
| CI/CD ready (macOS/Linux) | Yes | , |
| 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 | AskUI installer (standalone coming soon) | Windows installer |
Tip
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.