Aegis chief-of-staff

A calm operating layer for your work.

Aegis helps owners and small teams keep momentum: remember what matters, turn status into structured work, run local tools through explicit evidence, and meet you through CLI, MCP, channels, or agent plugins.

Install Aegis Explore Talents

Self-hostable by design

A durable brain, with your machine as the hands.

The Aegis control plane runs in Docker. The Local Gateway stays on your Mac or Windows machine for files, terminal, browser, GUI, and local MCP tools. Channels are optional surfaces; plugins can be the first way you use Aegis.

Quick install

Choose the path that matches your setup.

Full self-host needs Docker. Worker-only connects this machine to an Aegis Server you already run elsewhere.

macOS Apple Silicon

curl -fsSL https://raw.githubusercontent.com/HaloForgeAI/aegis-release/main/install.sh | bash

Installs the macOS arm64 CLI, creates the self-host directory, writes local config, and starts the Docker control plane.

Windows x64

iwr https://raw.githubusercontent.com/HaloForgeAI/aegis-release/main/install.ps1 -OutFile install-aegis.ps1
powershell -ExecutionPolicy Bypass -File .\install-aegis.ps1

Installs `aegis.exe`, prepares `~/.aegis/self-host`, and runs the same containerized control plane through Docker Desktop.

Worker-only

curl -fsSL https://raw.githubusercontent.com/HaloForgeAI/aegis-release/main/install.sh | \
  AEGIS_SERVER_URL="https://aegis.example.com" \
  AEGIS_ACCESS_TOKEN="owner-token" \
  bash -s -- --worker-only

Use this when the server lives elsewhere. It does not install a standalone non-Docker Aegis Server; this machine contributes tools and local context through the Local Gateway.

Before you start

Docker Desktop or Docker Engine + Compose v2 for full self-host
Optional LLM provider keys for provider-backed planning
Optional Telegram BotFather token if you want Telegram
Optional Codex / Claude Code plugins if agents are your main surface

Current release

Aegis v0.1.2 installs from public GHCR and GitHub Releases.

Full self-host pulls the official ghcr.io/haloforgeai/aegis:v0.1.2 image anonymously, then uses checksum-verified CLI archives from the public release repository. The Docker archive remains a recovery asset for constrained registries, not the normal install path.

View release

Ways to use Aegis

Start from the surface you already live in.

CLI and MCP

Inspect status, run readiness checks, expose Aegis MCP tools, and keep local tool execution explicit and auditable.

Agent plugins

Install the public Codex or Claude Code plugin so your coding agent can operate Aegis state and workflows through MCP.

Channels

Add Telegram or other channels when you want Aegis to meet you in chat. Channels are useful, not required.

Architecture

Control plane, Local Gateway, optional channels.

Aegis Manager plans through a real provider. Workers execute structured tool calls and return evidence. Chat messages, plugins, CLI, and MCP all feed the same operating system.

Docker control plane

Local Gateway on your host

Files · terminal · browser · MCP · channels

Talent Center

Aegis can discover capabilities without pretending every market feature is done.

Aegis already has Talent registry, runtime health, testkit, prepare gates, adapter handoff evidence, and MCP install-plan APIs. The public Talent Center starts as a curated catalog and grows into a reviewed marketplace.

Available now

Official seed catalogs, `GET /api/talent-center/mcp`, install plans, and public agent plugin distribution.

Next layer

Cloudflare Pages Functions or Workers for search, previews, publisher submissions, review queues, and signed catalog snapshots.

Not rushed

A real open marketplace needs identity, database-backed review, rollback, signing, tenant-safe permissions, and polished UI.

Agent plugins Installers Talent Center