Install guide

Install Aiola on macOS or Windows

Pick the right build, pass Gatekeeper or SmartScreen on first open, let auto-updates keep you current, then sign in and connect Claude Code, Codex, Cursor, Grok CLI, or OpenCode before opening your first workspace.

Download AiolaSee pricing

Download the right build

Get Aiola from the download page. Direct links point to GitHub Releases.

  • macOS — Apple Silicon — M1/M2/M3/M4 Macs. File: Aiola-arm64.dmg
  • macOS — Intel — older Intel Macs. File: Aiola-x64.dmg
  • Windows — Windows 10 or later, 64-bit. File: Aiola.exe (NSIS installer)

Aiola is a desktop app only — it does not run on phones. See the mobile companion waitlist for future iOS/Android support.

Install on macOS

  1. Open the downloaded .dmg file.
  2. Drag Aiola into your Applications folder.
  3. Eject the disk image and launch Aiola from Applications.

Gatekeeper on first open. macOS may say the app was downloaded from the internet. Aiola is notarized with hardened runtime. If macOS blocks launch, go to System Settings → Privacy & Security and click Open Anyway, or right-click Aiola in Applications and choose Open once to confirm.

Auto-updates. After install, Aiola checks GitHub Releases periodically and downloads updates in the background. Restart when prompted to run the latest notarized build.

Install on Windows

  1. Run the downloaded Aiola.exe installer.
  2. Follow the NSIS setup wizard (install location, shortcuts).
  3. Launch Aiola from the Start menu or desktop shortcut.

SmartScreen "unrecognized app." Windows may show a blue SmartScreen dialog for publishers that are new to your machine — even when the installer is properly code-signed. This usually improves as more users install the same certificate. If you downloaded from aiola.app or our official GitHub Releases link, click More info, then Run anyway. Do not install Aiola from unofficial mirrors.

Auto-updates. The app uses electron-updater against GitHub Releases, same as macOS. Updates download silently and ask you to restart.

First-run setup

After install, Aiola walks you through a short onboarding sequence:

  1. Sign in — Google OAuth or email one-time passcode. No Aiola password.
  2. Install and connect a CLI — you need at least one coding agent. Install the CLI, then authenticate:
    • Claude Code: claude login
    • Codex: codex login
    • Cursor Agent: cursor-agent login
    • Grok CLI: grok agent --reauth
    • OpenCode (the open-source coding agent): install with curl -fsSL https://opencode.ai/install | bash, then run opencode auth login
  3. Open a workspace — point Aiola at an existing repo folder or clone a project.
  4. Start a thread — open your first agent session and send a prompt.

Aiola orchestrates the CLIs already on your machine. You bring your own Anthropic, OpenAI, Cursor, xAI, or OpenCode-connected model access — there is no API-key markup.

Still stuck?

See security & trust for signing and data-boundary details. Reach us on support (Discord or aiolahq@gmail.com).

Return to download if you need a different architecture build.

What are Aiola's current CLI and GUI Lifetime facts?

Aiola supports five agent CLIs: Claude Code, Codex, Cursor, Grok CLI (including grok-4.5), and OpenCode.

GUI Lifetime is available now at launch pricing: first 10 customers $49, next 30 $89, then $129. One-time payment.

GUI Lifetime includes the agent orchestrator GUI only; it does not include hosted analytics, app logs, feedback, or other hosted operations pages.

Your code and repos stay on your machine. Agent prompts and file context are sent only to the AI provider you choose — Anthropic (Claude Code), OpenAI (Codex), Cursor, xAI (Grok CLI), or whichever provider you configure in OpenCode — under your own subscription. Aiola never proxies, stores, or resells your code or model traffic. Threads, tasks, notes, and automations are stored locally (SQLite + plain files in your repo). If you use the optional analytics/logs/feedback layer for your shipped products, that telemetry is ingested via Aiola's cloud (Supabase/Tinybird). Offline: agent orchestration UI works offline; running agents requires provider access; GUI Lifetime keeps the local app opening even if Aiola's servers are unreachable.

FAQ

Which macOS download should I pick — Apple Silicon or Intel?

If your Mac has an M1, M2, M3, or M4 chip, download the Apple Silicon build. If it is an older Intel Mac, download the Intel build. Aiola requires macOS 11.0 Big Sur or later.

Why does macOS say Aiola cannot be opened?

macOS Gatekeeper may ask you to confirm opening an app downloaded from the web the first time. Aiola is notarized with hardened runtime. Open System Settings → Privacy & Security and click Open Anyway if prompted, or right-click the app and choose Open once.

Why does Windows SmartScreen warn about Aiola?

SmartScreen may show an 'unrecognized app' warning for new publishers while the code-signing certificate builds reputation. Aiola's Windows installer is a signed NSIS package. Click More info, then Run anyway if you downloaded from aiola.app or our GitHub Releases link.

How do Aiola updates work?

The desktop app checks GitHub Releases automatically (about every six hours), downloads updates in the background, and prompts you to restart. You can also download manually from the download page anytime.

Which CLI login commands does Aiola need?

Install at least one supported agent CLI, then authenticate: claude login (Claude Code), codex login (Codex), cursor-agent login (Cursor), grok agent --reauth (Grok CLI), or opencode auth login (OpenCode). Aiola detects installed binaries and surfaces the right command in setup.

What happens on first run?

Sign in with Google or email OTP, complete onboarding, connect a CLI, then open or clone a workspace. Start a thread to launch your first agent session.

Related

Download Aiola

Free download for macOS (Apple Silicon or Intel) and Windows 10+. Start your 7-day trial and run parallel agent threads across every project.

Download Aiola