AO ships as a desktop application for macOS, Windows, and Linux. The core workflow is the same everywhere: register a repository, create an isolated worktree, run an agent in Chat or Terminal UI, and follow its pull request.
Desktop Downloads
| Platform | Available packages |
|---|---|
| macOS Apple silicon | Application zip and disk image |
| macOS Intel | Application zip and disk image |
| Windows x64 | Desktop installer |
| Linux x64 | AppImage, Debian/Ubuntu package, and Fedora/RHEL package |
Use the download selector on Installation for the current release. Installed builds check for updates on launch and periodically while running.
macOS
Both Chat and Terminal UI are supported. Install tmux if you want to use native terminal sessions:
brew install tmux
If you launch the app with ao start from a terminal and tmux is missing, it warns you and names this exact command to run.
macOS packages include both a .dmg and .zip. The disk image is convenient for first installation; the zip is also part of the release because the desktop updater uses it for future updates.
Linux
Linux supports the desktop app, Chat, tmux-backed Terminal UI, and the in-app browser inspector. Install tmux with your distribution package manager when needed:
sudo apt install tmux
If you launch the app with ao start from a terminal and tmux is missing, it warns you and names the exact
sudo command for whichever package manager it finds (apt-get, dnf, pacman, zypper, or apk). Run it
yourself: AO never asks for your administrator password.
Choose the AppImage for a portable launch, or the .deb/.rpm package that matches your distribution.
Windows
Windows supports the desktop workflow, structured Chat, and native Terminal UI through AO's conpty host. It does not require tmux, and iTerm2-specific helpers do not apply.
Use PowerShell, Command Prompt, or Git Bash for optional CLI commands. AO suppresses transient console windows for tools launched by the desktop daemon.
Mobile Companion
AO's Expo mobile app is a second interface to the desktop daemon, not a cloud relay. In desktop settings, choose Connect Mobile to enable a separate LAN listener and pair the phone.
Security properties:
- The LAN listener is off by default and exists only while Connect Mobile is enabled.
- It is protected by a rotating connection password.
- The pairing QR contains the address, not the password.
- Traffic is plaintext HTTP and intended only for a trusted home network.
- Daemon control, telemetry, and browser-control routes remain loopback-only.
Mobile defaults new workers and orchestrators to Chat when the selected harness supports it. Terminal UI remains available as a compatibility choice.
Remote And Server Use
The desktop daemon's primary listener is deliberately bound to 127.0.0.1 without authentication. Do not expose it through a public bind or reverse proxy. Connect Mobile is the only built-in off-device listener and is deliberately limited to an explicitly enabled home-network workflow.
For unattended work, keep the desktop host awake and reachable on its local network. AO does not turn the local desktop product into a hosted multi-user service.