Install Aegis0.7.10

Governed access to Amazon Bedrock from the coding tools you already use.

1Install

macOS & Linux

bash -c "$(curl -fsSL 'https://aegis.hatchery.com/download?platform=install-sh')" install.sh 'https://aegis.hatchery.com'

Paste into Terminal — Cmd-Space, type Terminal, Enter. Any folder. It installs Aegis to ~/.local/bin and runs aegis init for you.

Rather download the files yourself?

The installer zip. Holds the macOS and Linux binaries, the installer, and USING-AEGIS.md, the full guide. This path does not run aegis init — the Installed from a zip, or repairing a machine? section below covers it.

Download installer (.zip)

unzip aegis_0.7.10.zip && ./install.sh

Paste into Terminal, in the folder the zip downloaded to (usually Downloads). The installer detects your platform, installs to ~/.local/bin and clears macOS quarantine.

Windows

& ([scriptblock]::Create((irm 'https://aegis.hatchery.com/download?platform=install-ps1'))) -ApiBase 'https://aegis.hatchery.com'

Paste into PowerShell — press Win, type PowerShell, Enter. Any folder. It installs Aegis and runs aegis init for you. No administrator rights needed.

Rather download the files yourself?

The binary on its own. Rename it to aegis.exe and put it in a folder you intend to keep — %LOCALAPPDATA%\Programs\Aegis is where the command above puts it. Then, from that folder, run .\aegis.exe init --config-url https://aegis.hatchery.com/config; it adds itself to your PATH, so every later command works from anywhere.

Download for Intel/AMD Download for ARM

Or the installer script as a file. Save it, then run it from the folder it landed in.

cd ~\Downloads
powershell -ExecutionPolicy Bypass -File .\install.ps1 -ApiBase https://aegis.hatchery.com

Paste into PowerShell after saving the script. The cd is the step people miss: the script is only found from the folder it is in.

Your operating system may warn you. The Windows builds are code-signed by Hatchery LLC — if SmartScreen still appears on a new release, the publisher it names is us. The macOS builds are signed with Hatchery LLC's Apple Developer ID and notarized by Apple; Gatekeeper checks that online on first run, so the first launch needs a network connection. On first run Windows may also ask about the firewall — you can decline: Aegis listens only on 127.0.0.1 and does not need the exception.

Installed from a zip, or repairing a machine?

The one-line installers above already ran the whole setup — there is nothing more to do on that path. If you downloaded the files yourself instead, or want to repair a machine, one command does the same job, and re-running it is always safe:

aegis init --config-url https://aegis.hatchery.com/config

Open a new terminal and paste this.

No environment variables and no AWS account needed. aegis init puts aegis on your PATH, signs you in, points your tools at Aegis, starts the proxy, then sends a real request to prove it works. It shows every change before making it and merges into your existing settings rather than replacing them. Add --dry-run to look without writing; run aegis doctor any time to see what is and is not working; aegis setup undo reverses the file changes.

The individual steps still exist if you want just one: aegis login, aegis setup, aegis proxy start, aegis proxy autostart enable.

2Use your tools

Most tools need nothing from you beyond a new terminal. aegis setup undo reverses every file change below.

Claude Code — nothing to do. Configured through ~/.claude/settings.json; open a new terminal.
Codex CLI — nothing to do. Configured through ~/.codex/config.toml; open a new terminal.
OpenAI SDKs, aider and any OpenAI-compatible client — nothing to do. OPENAI_BASE_URL is set in your shell profile; open a new terminal so it loads.
Cursor — not supported yet. Cursor sends every model request through its own servers, so its base-URL override cannot reach the Aegis helper on your machine, and a governed path for Cursor has not been built or tested. Until it has, Cursor is not a supported tool. Claude Code and Codex CLI work from Cursor’s terminal the same way they do from any other.
Claude Desktop — one step inside the app, no administrator needed. Aegis writes ~/.aegis/claude-desktop-import.json. In Claude Desktop, signed out of any claude.ai account: Help → Troubleshooting → Enable Developer Mode, then Developer → Configure Third-Party Inference…, open the configuration picker at the top right → Import configuration…, choose that file, click Apply Changes. The app relaunches and offers the Aegis option on its sign-in screen. aegis doctor confirms it took effect. The portal’s Docs page walks through it with screenshots. Administrators rolling out a fleet get the same settings as a managed profile beside it (.mobileconfig on macOS, .reg on Windows).
The ChatGPT desktop app cannot be pointed at Aegis, and no setting changes that. It signs in with a ChatGPT account rather than as an API client, and there is no endpoint option, environment variable, or managed-configuration key that redirects it. The coding agent inside it reads ~/.codex/config.toml, which Aegis does configure; the chat does not go through the gateway. If you need model traffic from a desktop app on Aegis, Claude Desktop is the one that supports it.
Web search is off unless your organisation turns it on. Claude Code’s WebSearch returns an error through Aegis, and Codex’s web search is switched off, until your administrator enables web search for your team. Once enabled, each search query is checked against the Aegis content policy before it leaves the gateway, and searches are metered. Other server-run tools (web fetch, code execution, memory) are not available through Aegis.
Anything else — point it at http://localhost:18080 and send requests without an API key.

3Models

Use these names wherever your tool asks for a model.

claude-opus-5most capable

claude-sonnet-5faster

claude-opus-4-8previous

claude-opus-4-7previous

claude-haiku-4-5small & fast

gpt-oss-120bopen-weight

gpt-oss-20bopen-weight

Prompts are inspected against the Aegis content policy before reaching the model, and blocked when they violate it. Model output is inspected the same way. Inspection is enforced by AWS in a separate account, so it cannot be turned off from the gateway. Prompt and completion content is not retained.

Frontier OpenAI models — enabled per team, so these may not be turned on for you.

gpt-5.6-solfrontier

gpt-5.6-terrafrontier

gpt-5.6-lunafrontier

gpt-5.5frontier

gpt-5.4frontier

The frontier models come with a different guarantee. They run on a separate AWS surface from everything above. Prompts are inspected against the Aegis content policy before reaching the model, and blocked when they violate it. Inspection is enforced by the gateway rather than by AWS, and model output is not inspected on this path. AWS retains requests and responses for up to 30 days for safety and abuse prevention, and does not share them with the model provider. We retain no prompt or completion content. For the models in the first group AWS enforces inspection, so it holds even if the gateway is wrong; for these it does not. Same inspection, weaker enforcement, real retention — worth knowing before you put anything sensitive through them, and worth raising with your administrator if it matters for your work.

Web search is a separate, metered feature. Web search is off unless an administrator turns it on for your organisation. When it is on, each search query a tool runs through Aegis is metered and billed per query at the price shown beside the setting, in addition to the model usage that asked for it. A frontier OpenAI model usually runs two or three queries for one search. Search queries are checked against the Aegis content policy by the Aegis gateway before they leave it, and results come from a search index operated by AWS. That check is enforced by the gateway rather than by AWS, so web search carries the frontier models' weaker guarantee whichever model asked for it.

The authoritative list for your access is whatever GET /v1/models returns through the proxy — a name missing there is one your team has not been granted, not one that is broken.

4If something is wrong

aegis doctor          # what is and is not working, end to end
aegis ui              # the same thing as a page in your browser
aegis status          # are you logged in, and until when
aegis proxy status    # is the proxy running
aegis login           # sign in again
aegis init --dry-run  # what would change, without changing it
aegis setup undo      # put everything back

aegis doctor is the one to reach for first: it re-reads every file from disk, checks PATH the way a new shell would see it, and finishes with a real request, so a configuration that looks right but does not work cannot pass. aegis ui shows the same thing as a page served by the proxy on your own machine — status, the models your key can invoke, sign-in, and the Claude Desktop profile as a download button. It is never shown your credential.

aegis setup undo reverses everything setup changed — your PATH entry, Claude Code’s settings, the Codex provider — except Claude Desktop, whose configuration lives inside the app; the way to remove it is printed for you. Before Aegis first modified any file it saved an untouched copy beside it as <file>.aegis-original, written once and never changed.

A 401 or 403 usually means the session expired — run aegis login. Connection refused on port 18080 means the proxy is not running — run aegis proxy start.

Individual binaries

macOS ARM macOS Intel Linux x86-64 Linux ARM

A binary saved by the browser is not executable yet, and on macOS it is quarantined and unsigned — run xattr -d com.apple.quarantine aegis-darwin-arm64; chmod +x aegis-darwin-arm64 (adjust the filename) before first use. The one-line installer above handles all of this.