Install Agora

Agora comes in three shapes — the desktop app, a portable copy, and a command-line tool — and all of them live on the same GitHub releases page. This page gets you the right download and explains how to read that page when you come back for more.

See what Agora looks like first Read the task guides

Quick download

The button offers the standard desktop installer for the system you are on. If it cannot detect your platform, the sections below show how to pick the file by hand.

⬇ Download Agora

Latest release v0.9.3

All platforms →

Ignore releases tagged registry-* — download the app file for your OS.

⚠️ We couldn't find a download for your platform. On the releases page, download the file for your platform (.exe, .dmg, or .AppImage). Ignore releases tagged registry-* — those are catalog updates, not the app itself.

Which Agora should I install?

Every release ships all three builds, and they are not mutually exclusive: the app and the CLI use the same data root on a machine, so you can add one later without moving your instances. The portable copy is the exception — it deliberately keeps everything in its own folder.

Desktop app

Recommended for most users

The standard, installed experience: Start menu entries on Windows, Applications on macOS, your package manager on Linux.
Keeps saved sign-ins in your operating system’s credential store, alongside your other apps.
Has an update check built in, so newer versions are offered from inside the app.
Pick this unless you have a specific reason for one of the other two choices.

Portable

Windows only · nothing to install

Everything Agora needs is inside one ZIP. Extract it into any writable folder and run it — nothing is installed, and there is nothing to uninstall.
Application data lives in a data folder beside the executable, so the whole setup fits on a thumb drive and works on machines you do not control.
Reduced security, by design: saved sign-ins are encrypted inside that folder instead of your operating system’s credential store, so anyone who can read the drive can read them. Keep the drive safe.
Updates are manual: close Agora, replace the executable from a newer portable ZIP, and keep portable.txt and your data folder. Do not run the installer to update a portable copy.

CLI

Advanced users and AI agents

The agora command in a terminal, shipped as a standalone archive with no installer. Unpack it and put the binary wherever you keep tools.
The same core as the desktop app — instances, installs, health checks, launches, snapshots — plus --json output for scripts.
Made for scripting, support diagnostics, and local AI agents through MCP.
Everyone else should stay on the desktop app. The CLI can change the same data as the desktop app, so do not run both against one instance at the same time, and read the safety rules before experimenting.

CLI reference MCP and external AI tools

Understanding the releases page

The releases page holds two different things, and only one of them is something you install. Knowing the two apart is the whole trick.

App releases and catalog releases

v1.2.3 — an app release. The tag starting with v is the version, and the release carries the installers and archives for it. This is the family to install from.
registry-2026-08-27 — a catalog snapshot: the curated catalog database, published with the date as its tag. Agora downloads and verifies those for itself; there is nothing here for you to install, and these releases can be ignored entirely.

GitHub gives its “Latest” badge to the newest ordinary release, and catalog snapshots are ordinary releases — so the badge, and any “releases/latest” link, can point at a catalog snapshot. Ignore the badge: open the newest release whose tag starts with v.

What the file names mean

Every app release follows one pattern, so the important parts are readable before you download anything:

agora-desktop-v1.2.3-windows-x64-setup.exe

agora: The product name. Every download starts with it.
desktop / cli: Which Agora this is: the desktop app, or the command-line tool.
v1.2.3: The version. Every file in one release carries the same one, so you never have to mix versions.
windows / macos / linux: The operating system the file is built for.
x64 / arm64: The processor architecture. x64 covers Intel and AMD machines (including Intel Macs); arm64 is Apple Silicon. Older releases write these as x86_64 and aarch64.
setup / msi / portable / dmg / AppImage / deb / rpm: The package format. The next section says which to pick.

Which file do I pick for my system?

Windows

...-windows-x64-setup.exe — the standard installer. Start here.
...-windows-x64.msi — the same app packaged as an MSI, for managed or scripted installs.
...-windows-x64-portable.zip — no install; see Portable above.

macOS

...-macos-arm64.dmg — Apple Silicon (M-series chips).
...-macos-x64.dmg — Intel Macs.
Not sure which you have? Apple menu → About This Mac: “Chip” means Apple Silicon, “Processor” means Intel.

Linux

...-linux-x64.AppImage — runs on most distributions; mark it executable and run it.
...-linux-x64.deb — Debian, Ubuntu, Mint, Pop!_OS, and friends.
...-linux-x64.rpm — Fedora, RHEL, openSUSE, and friends.

Command line

agora-cli-v1.2.3-windows-x64.zip on Windows, and .tar.gz archives for linux-x64, macos-x64, and macos-arm64.
Unpack it and put the agora binary wherever you keep tools — there is no installer.

The files that are not installs

...-macos-arm64.app.tar.gz (and its x64 twin) — macOS updater archives. Agora’s update check fetches these itself; you never install from them by hand.
latest.json — the metadata that update check reads. You never need to download it yourself.
SHA256SUMS — one list of SHA-256 hashes covering the installers and archives in the release. Optional but quick: on Linux or macOS, with the release files in one folder, run sha256sum -c SHA256SUMS; on Windows, compare a file’s Get-FileHash output against the list.

Everything above lives on the releases page. Newer app releases open with a direct-download table in their notes. Underneath, GitHub keeps the full asset list alphabetical (CLI builds before desktop builds) and folds it behind “Show all assets” when it is long — expand it for files the table does not cover, such as the .msi or .debinstallers.