Start local testing with Aegora Desktop.

Choose your Desktop installer

Check your processor in macOS About This Mac or Windows Settings → System → About. Choose the matching architecture.

Before you install

Allow at least 4 CPUs, 12 GiB of memory for Docker and 20 GiB of free disk. Desktop checks Python 3.12+, OpenSSL, Docker Engine with Linux containers and Docker Compose 2.24.4+ and provides install/help actions. Complete license and operating-system prompts yourself, then recheck the device.

No source checkout, Go or Node installation is required. Downloading Runtime images also requires network access and, for private registries, your own authorized registry sign-in. A candidate code is supplied separately when required.

Install and set up locally

1. Download and install Desktop. Verify the installer SHA-256 against the trusted release or private handoff. Install the matching DMG or EXE and launch Desktop.
2. Let Desktop guide Runtime installation. Choose Complete Local Install, then Check prerequisites. Complete any install/help prompts and choose Recheck device. Enter your candidate code if supplied and choose Install and start. Desktop verifies the pinned Runtime archive and starts the reviewed images.
3. Complete administrator setup. Choose Show initial sign-in and Open Admin Console. Use the generated tenant and credentials, then rotate the initial password before a session is issued. Keep the replacement password private.
4. Set up plugins and start testing. In the local Console choose Create Agent Access token. Grant context/read scopes and add draft scope only when saving inactive drafts. Back in Desktop choose Secure local token, Set Up Local Plugins, then Configure Codex/Claude. Restart your authoring client. Use Open Admin Console, Open Event Console, Refresh status and Show support summary to test and diagnose the installation.

Follow your candidate scenario sheet with synthetic data. Cover policy denial, approval, human fallback, tenant isolation, independent outcome evidence and restart recovery. Plugin access does not grant approval, activation or execution authority. Runtime keeps decisions, governance, execution and audit evidence within the tenant boundary.

Stop Runtime preserves local data; Start Runtime resumes the same installation. Send the candidate version, OS, architecture and sanitized support summary when reporting a failure. Never send passwords, tokens, .env files or backups.

Separate authoring and Runtime downloads

These packages have their own tested support scope. For guided local setup, use a Desktop installer explicitly listed above.

Support boundaries

Curated templates demonstrate native Aegora design patterns. Sample traces do not certify vendor targets. Approval, credentials and activation remain tenant-governed. Downloads are not counted as usable installations or evidenced runs.