Install ORG-2

ORG-2 is a desktop application built with Rust and Tauri v2, so there is nothing to host and no server to run — you install a single app and it keeps its data on your own machine. This page covers the download assets, what happens the first time you launch, the optional native helpers, how updates arrive, and how to build from source.

Download

Prebuilt assets always resolve through GitHub's "latest release" pointer, so the links below never go stale.

Every asset produced by a release, including the per-version filenames, is listed on the latest release page.

Note: The release pipeline currently runs two build jobs — macOS aarch64-apple-darwin and Windows x86_64-pc-windows-msvc. If a Linux asset is not attached to the release you are looking at, build from source instead using the steps at the end of this page.

System requirements

• macOS: Apple Silicon. The bundle declares a minimum system version of macOS 10.15.
• Windows: 64-bit (x64). Both the .exe and the .msi install the same application.
• Linux: x64, when a build is published for that release.
• Disk: the app itself is designed to stay under 100 MB on disk. Your data directory grows separately as you run sessions.

Windows: installer or MSI?

The -setup.exe is the NSIS installer and is the right choice for a normal single-user install. The .msi exists for environments that deploy software through MSI tooling. Pick one; installing both is not supported.

macOS: signing and first launch

Release builds are signed with an Apple Developer ID certificate and notarized during the release workflow when the signing secrets are configured. A signed, notarized .dmg opens normally: drag ORG2 into /Applications and launch it.

If you built the app yourself without signing, macOS Gatekeeper will refuse the first launch — that is expected for an unsigned local build, not a problem with the download.

Windows artifacts are signed through Azure Trusted Signing in the same workflow, again only when the signing credentials are present.

What happens on first launch

1. Login screen. ORG-2 opens on a sign-in page. You do not need an account: choose Continue without signing in to run entirely on your own keys. That choice persists until you sign in or sign out.
2. Setup walkthrough. The first-run wizard walks you through six steps, listed down the left side: Welcome, Theme, Dev Passport ("Set up Dev Passport"), GitHub, Workspace ("Open a Workspace"), and Complete. Move with Continue and Back, jump to any step by clicking it, or press Skip Setup at any point. The final step's button is Get Started.
3. Workstation. Finishing or skipping the walkthrough drops you into the Workstation, the main working surface.

Nothing in the walkthrough is mandatory — GitHub and the workspace can both be connected later. See Quickstart for a guided first run.

Optional native sidecars

Two features rely on native helper binaries that are deliberately not bundled into the signed app:

Sidecars are installed lazily into ~/.orgii/bin/, never during startup — a slow network must not hold the app behind its splash screen. Install them from Settings → Computer Use → Sidecar Downloads, where each row shows Installed / Not installed / Unsupported and a Download action, plus a Refresh status control.

Without them, Browser Use and Computer Use either fall back to a binary found on your PATH or stay unavailable. Nothing else in the app is affected — sessions, tools, memory, and replay all work without sidecars.

When developing from source, pnpm run download:sidecars fetches the same binaries into src-tauri/bin for the current OS and CPU. If a sidecar is missing at build time the Rust build writes a small placeholder resource so the build still succeeds.

Updating

ORG-2 ships with the Tauri updater. It checks for a new version at startup and then once an hour. When one is found:

• A Download update button, labeled with the new version number, appears at the bottom of the navigation sidebar.
• Clicking it opens an update dialog with Update, Later, and Skip this version. Skipping suppresses that specific version for the rest of the run.
• Choosing Update downloads with a progress bar, installs, and relaunches the app.

You can also check manually from Settings → App Update, which shows Current Version and a Detect Update action.

Note: The updater manifest generated by the release workflow currently carries a darwin-aarch64 entry. On Windows, download and run the newer installer to update.

Where your data lives

Everything ORG-2 stores locally lives under ~/.orgii/:

A background housekeeping pass runs ten minutes after boot and trims the long tail: logs, plan files, Merkle snapshots, file history, and the session/event cache are kept for 30 days; browser screenshots for 7. Orphaned per-session directories are evicted once their session is gone.

Settings → Storage shows the data directory and log files with their on-disk sizes, plus Open folder and Reveal in folder actions.

Building from source

Prerequisites, per the repository's contributing guide:

Then, from the repository root:

pnpm install
pnpm run download:sidecars
pnpm run tauri:dev

pnpm run tauri:dev starts the webpack dev server through Tauri's beforeDevCommand and opens the app; use the Tauri scripts rather than launching the frontend on its own. For faster iteration against a packaged bundle, pnpm run tauri:build:fast rebuilds only the app target for the local development profile and opens the result.

Before opening a pull request, run the checks that match what you changed: pnpm run lint, pnpm run test, and pnpm run check:circular for the frontend; pnpm run cargo:check, pnpm run cargo:clippy, and pnpm run cargo:test for Rust.

ORG-2 is licensed AGPL-3.0-or-later.

Next steps

• Quickstart — a ten-minute first run, from setup walkthrough to your first replay.
• API keys — add provider keys or sign into an agent CLI.
• Concepts — how sessions, trajectories, and workspaces fit together.
• Troubleshooting — what to check when the app or a session misbehaves.