Aether documentation

Set up the server and client, link them over SSH or Tailscale, and finish your first Claude Code or Codex run in about ten minutes.

How to install the aether-server binary on Linux and the aether client on Linux, macOS or Windows, plus running the server as a service.

How Aether reaches your server over one SSH port, why Tailscale is the recommended network and identity layer, and what stays closed by default.

How to invite teammates to a shared Aether server, what the viewer, collaborator and admin roles can do, and setting per-workspace spending budgets.

What a member's environment is, how aether env save commits a custom container image, and when Aether falls back to the standard image.

The environment terminal, a persistent per-member shell container with your home mounted at $HOME, surviving reconnects and new runs.

The server-owned home directory mounted into every one of a member's containers, and what it keeps: logins, config and installed tools.

The agent CLIs Aether can launch, how a harness teaches it to start one, and the rules for installing and logging in to each vendor tool.

How to add a new agent CLI to Aether as a harness profile, and optionally turn its output into typed events with an adapter.

Aether's security stances: the container is the isolation boundary, agents run as root by default, and what the dashboard gateways expose.

How the dashboard reaches your server through aether gui on your machine or aether-server --web-port on its tailnet, and how they differ.

How the Aether dashboard's browser client is built: Next.js, React and TypeScript, served through either dashboard gateway.

How Aether's conflict radar flags runs editing the same files and gives them an advisory channel to talk, without locking anything.

How Aether assembles evidence submissions for a candidate revision and lands or proposes it, kept separate from mission state.

What happens when the server reboots, fills up or loses connections, the tuning flags available, and where each behaviour is proven.

The optional MCP bridge that exposes six coordination tools in-container, alongside the canonical aether-internal CLI every run gets.

How Aether is tested: unit tests beside their packages, plus an integration and E2E suite behind a build tag covering failure scenarios.

The privacy policy for the Aether Android app and the dashboard it shows: what the app stores on the phone and what it sends to your server.

How to contribute to Aether: read the docs and the package you're changing first, search for existing helpers, and keep credentials out of the checkout.