Install Aegis

Choose Your App

Platform	Primary install asset	Use it for
macOS	Aegis-<version>-macos-arm64.dmg	Main desktop app, Core control, Local Gateway, Workbench, Chat, mobile pairing.
Windows	Aegis-<version>-windows-x64.msix	Main desktop app, Core control, Local Gateway, Workbench, Chat, mobile pairing.
iPhone / iPad	TestFlight or signed Aegis-<version>-ios.ipa	Mobile Chat, approvals, notifications, share/voice/location context, Native Node work.
Android	signed Aegis-<version>-android.apk or Aegis-<version>-android.aab	Mobile Chat, approvals, notifications, share/voice/location context, Native Node work.

Download

Use the latest release assets from HaloForgeAI/aegis-release. Verify SHA256SUMS before installing when the checksum file is available.

macOS

1. Download Aegis-<version>-macos-arm64.dmg.
2. Open the DMG.
3. Drag Aegis.app into Applications.
4. Launch Aegis and allow the permissions you want Aegis to use.
5. Use the desktop app to start Core, inspect health, and pair mobile devices.

The macOS app is the primary owner surface. It should include the desktop shell and bundled Core/CLI runtime for local operation, then expose Workbench, Chat, Local Gateway, and pairing from the app.

Choose the Core URL for mobile devices from the Network Access guide before generating pairing links.

Windows

1. Download Aegis-<version>-windows-x64.msix.
2. Open the MSIX package and install Aegis.
3. If MSIX signing is not available for a development release, use the provided portable zip only for trusted testing.
4. Launch Aegis from Start.
5. Use the desktop app to start Core, inspect health, and pair mobile devices.

The current Windows release target is MSIX because the app is a Windows App SDK / WinUI native app. MSI packaging is an enterprise installer follow-up and should not be treated as available until the release CI emits a signed MSI asset.

Choose the Core URL for mobile devices from the Network Access guide before generating pairing links.

iPhone / iPad

1. Prefer TestFlight when a public or private testing link is available.
2. For direct testing, install a signed Aegis-<version>-ios.ipa through Apple Configurator, Xcode Devices, or an MDM path approved by the owner.
3. Open Aegis and pair it with Aegis Core using a QR code, setup link, or manual Core URL plus scoped node token.
4. Approve iOS permissions only when you want that capability enabled.

iOS IPA export requires Apple signing assets and a provisioning profile. A local Personal Team is enough for direct owner-device testing, but broader TestFlight/App Store distribution requires an enrolled Apple Developer Program team.

Android

1. Download the signed Aegis-<version>-android.apk for direct install, or use Aegis-<version>-android.aab for Play Console style distribution.
2. If sideloading an APK, install only signed release assets from a trusted Aegis release.
3. Open Aegis and pair it with Aegis Core using a setup link or manual Core URL plus scoped node token.
4. Approve Android permissions only when you want that capability enabled.

Unsigned APKs are build artifacts only. They are not user-installable release assets.

First Run

1. Open the desktop app on macOS or Windows.
2. Start or connect to Aegis Core from the Runtime / Workbench surface.
3. Configure provider secrets from the app settings or the managed Core profile when AI planning is needed.
4. Pair iPhone, iPad, or Android from the desktop pairing card.
5. Send a short Chat request and confirm that the response, task state, and evidence are visible.

Advanced Operator Paths

CLI, MCP, and agent plugins remain supported for operators and AI coding tools. They should connect to an existing Aegis Core or to the Core managed by the desktop app.