AerieOSFeatures
What AerieOS does today. The changelog says what changed in each release.
Agents and sessions
Four agents and any model
Claude (Claude Code), ChatGPT (Codex CLI), Copilot (Copilot CLI), Grok (Grok Build), and any model through a node's model router (OpenCode), each held to the same briefing, house rules and guards.
Real terminals in a dock
At the foot of every page, at a desk or on a phone, each session in its own project's view of the disk. Resume, restart, pick the model and effort.
Briefed before the first word
A session starts with the project's house rules, roadmap and open bugs, and is told when the project changed under it.
Storage, on the installed editions
Pools and an array
ZFS pools, or an array of mixed disks with parity, a pool for each purpose, snapshots and backups.
Shares
SMB and NFS shares with per-person access, Time Machine included.
Moving a NAS you have
Disks another system made are taken as they are, never formatted: read-only by default, the shares served again, the containers and VMs that ran brought back.
Projects
A page per project
Overview, rules, roadmap, bug tracker, git, tests, static analysis, artifacts, containers, VMs, wiki and design, shared with every session.
Builds, tests and CI
Builds and tests run on the project's node and are timed and recorded; a node can run a project's suites as a job, or be a self-hosted GitHub Actions runner.
Android end to end
An emulator per project, a real phone lent through the companion app, screenshots and frame-by-frame reels a session can read, and release signing with keys no session ever sees.
Machines
Nodes in one script
Ubuntu, Debian, Fedora, Rocky Linux, AlmaLinux, CentOS Stream, Arch Linux or openSUSE, each walked end to end on a real machine.
One Library
Coding agents, toolchains, tool packs from a vetted catalog or your own, services and apps, as one store of cards per node.
Containers and hosting
A compose file becomes a running instance in one click; an nginx per node puts a hostname and a certificate in front of it.
Virtual machines
From a cloud image or an installer's ISO, Windows included, each on its own network, with snapshots, USB passthrough and its screen in the dock.
People and safety
Roles and dials
Accounts with roles and per-project access, and a dial for everything a session may do on its own: allowed, asked, or refused.
Sign-in
Two-factor sign-in and passkeys; the bell reaches you by email, a webhook, ntfy, Gotify, Pushover, Telegram, Discord or Slack.
Secrets kept sealed
A key made at install seals what the controller keeps; each person has a store of their own for their agents' sign-ins and git tokens.
A controller that moves
Prepare to move arms a move to another home; every node hears where and follows by itself.
