Install
Not ready for production. Use it at your own risk.
AerieOS is early, experimental software that changes fast. Its coding agents edit, commit, run and push code on your machines, and its storage takes over disks. Run it only on machines you can wipe, on repositories made for testing, and with data you have backed up elsewhere or can afford to lose. Nothing in it has been audited, and it comes with no warranty of any kind.
Pick AerieOS for the AI workshop and the NAS on a machine of its own, or Aerie Workshop for the AI workshop alone, as a container on a host you already run. Then open its page, make the owner, and enroll a machine to do the work.
What you need
- A place for the controller: a host with Docker, a Linux machine of its own, or a machine or VM you can wipe for AerieOS.
- At least one node, unless the controller is its own: a Linux machine or VM on Ubuntu 24.04 or later or Rocky Linux 9, the systems nodes are tested on. A separate VM keeps what the agents run away from your server.
- Your repositories on GitHub, Gitea or Forgejo, or any git remote.
- An account with a coding agent: Claude, ChatGPT, Copilot or Grok, signed in from the dashboard.
1. The controller
Aerie Workshop, as a container
The AI workshop alone, on any host with Docker; the storage comes with the two below. This is the minimal shape; the repository's docker-compose.yml carries every setting with what it does.
services:
aerie-workshop:
image: ghcr.io/aquilaelabs/aerieos:latest
restart: unless-stopped
ports:
- "7680:7680"
volumes:
- ./config:/config
- ./workspace:/workspacedocker compose up -dPin a release (:0.9) rather than :latest to choose when you move; :dev follows the dev builds.
AerieOS, on a Linux machine of its own
git clone https://github.com/aquilaelabs/aerieos.git
cd aerieos
sudo nodes/install-controller.sh --installThe machine is the controller and its own first node, and updates come from the dashboard.
AerieOS, as its own OS
Download builderbot-os-VERSION.iso from the releases, boot it, pick a disk. Or write a stick that runs it from memory with the stick maker. Both are new in 0.9: use a machine or a VM you can wipe.
2. Make the owner
Open http://THE-HOST:7680. The first account made is the owner. Do it right away: until then, anyone who reaches the page can claim it.
3. Enroll a node
On the Nodes page, Enroll node writes a script for the machine. Run it there as root and the node appears, enrolled. A bare-metal or OS controller is already its own node.
4. Add a project
New project on the Projects page, its repository added on its card, then Start agent. The session starts on the project's node, briefed with its rules and plan.