macOS
Aegis-<version>-macos-arm64.dmg
Install Aegis.app from the DMG. The desktop app manages local Core, Local Gateway, nodes, Chat, Workbench, and runtime status.
Aegis assistant hub
One Core for your AI work, devices, and agents.
Aegis gives you a stateful personal AI runtime: natural-language planning through real providers, explicit local execution through Gateway and Native Nodes, modern desktop and mobile apps, approvals, memory, and evidence you can inspect.
Owner-first architecture
Core owns state. Apps and nodes bring the interface and hands.
Aegis Core keeps sessions, tasks, approvals, memory, tools, channels, provider traces, and evidence. Native apps are the daily user experience. Local Gateway and Native Nodes execute explicit payloads on computers and devices instead of guessing from prose.
Quick install
Choose the path that matches your setup.
Aegis is moving to native application installs first. Start with the app for your platform, then choose how your devices reach Aegis Core.
Windows
Aegis-<version>-windows-x64.msix
Use the signed MSIX when available. Portable zip builds are for trusted testing only; MSI is an enterprise follow-up.
Mobile
iOS/TestFlight · IPA · Android APK/AAB
Pair iPhone, iPad, or Android as daily Chat and approval surfaces, and as Mobile Native Nodes where platform permissions allow.
Connection choices
- Local-only for one computer
- LAN for trusted home or lab networks
- Tailscale Serve for private owner-device access
- Cloudflare Tunnel for stable HTTPS hostnames and webhooks
- Public VPS only with Aegis auth and scoped tokens
Current release
Native app assets are the public install target.
Public releases should expose DMG, MSIX, APK/AAB, optional IPA, and checksums, with the docs covering platform install and Core connection choices.
Native surfaces
Use Aegis from Chat, Workbench, CLI, mobile, or your coding agent.
Desktop app
Start and inspect Core, manage Local Gateway, use session-based Chat, review tasks, approve sensitive work, and see evidence in Workbench.
Mobile app
Chat on the go, receive notifications, review approvals, capture voice or share-sheet context, and pair the phone as a Mobile Native Node.
CLI, MCP, and agents
Run diagnostics, expose MCP tools, connect Codex or Claude Code, and keep automation auditable through the same Core state.
Architecture
Aegis Manager plans. Workers and nodes execute explicit calls.
Ordinary chat and channel messages go through Aegis Manager and a real provider. Workers, Local Gateway, and Native Nodes receive structured tool or task payloads, execute them, and record evidence. Channels are useful surfaces; they are not the product's hidden parser.
Aegis Core
Manager · Gateway · Sessions · Evidence
Desktop · mobile · Local Gateway · agent runners
Talents and release path
Installable capabilities with honest status labels.
Aegis already has Talent registry, runtime health, testkit, prepare gates, adapter handoff evidence, and MCP install-plan APIs. Public-facing material must separate release-ready user paths from source-ready or phase-test-pending development evidence.
Release notes
Public release notes should only describe assets and workflows that are actually available and verified for users.
Available capabilities
Official seed catalogs, `GET /api/talent-center/mcp`, install plans, and public agent plugin distribution.
Next layer
Reviewed marketplace flows need identity, database-backed review, rollback, signing, tenant-safe permissions, and polished UI before they are called complete.