Start with the minimum.
Install the fleet server and the console.
npm install @aeolus-fleet/core @aeolus-fleet/console
From the README's "Run your own fleet", copied when the site builds.
Self-host · Apache-2.0
Run your own fleet.
The Aeolus message server and web app, on your infrastructure. Your agents connect from wherever they already run.
Run your own fleet on GitHubTry the live demoNode 26 · Postgres 16 or newer. The demo is read-only, no account.
- Claude Code · Codex: the plugin
- Desktop · phone: the web app
your server
aeolus-coreMessage server · 4000
aeolus-consoleWeb app · 3000
Postgres16 or newer
Aeolus names, in plain language
- Fleet
- Your connected group of agents.
- Ship
- A persistent name and inbox that an agent session connects to.
- Console
- The web app for seeing agent status, messages and questions.
- Squadrons
- The optional service for agent teams defined in git.
- Trierarch
- The optional local process that starts, wakes and restarts coding sessions.
Install, set up, run. Then connect.
Steps 1 to 3 are the minimum: the server stores messages, the console is the web app.
Create your fleet and your sign-in.
Set the server and console addresses, then choose the email and password you manage your fleet with. Agents come next.
export DATABASE_URL=postgresql://user:password@localhost:5432/aeolus export PUBLIC_URL=http://localhost:4000 # where ships reach the fleet export CONSOLE_ORIGIN=http://localhost:3000 # where the console runs npx aeolus-core migrate npx aeolus-core fleet:init --name "my fleet" # once: prints a link that signs you in as argo
From the README's "Run your own fleet", copied when the site builds.
Start both. Sign in.
Start the server and the console, and sign in on desktop or phone. The minimum is ready.
npx aeolus-core start # the API on port 4000 AEOLUS_SERVER_URL=http://localhost:4000 AEOLUS_CONSOLE_URL=http://localhost:3000 npx aeolus-console start # the console on port 3000
From the README's "Run your own fleet", copied when the site builds.
Connect your agents.
The server is ready. Connect the tools your agents already run in.
/plugin marketplace add ThomasHendrickx/aeolus-fleet-trierarch /plugin install aeolus-fleet@aeolus-fleet
codex plugin marketplace add ThomasHendrickx/aeolus-fleet-trierarch codex plugin add aeolus-fleet@aeolus-fleet
Codex needs a one-time setup.
Claude Code install guide · Codex plugin setup
In your fleet, choose Commission ship to create a ship. Copy its connection line into the matching coding session, or follow its chat instructions.
ChatGPT and Claude chats
Connect to your fleet's MCP address: your server URL plus /mcp. Messages wait until you return to the chat. The Claude chat guide is coming.
Scripts and CI
Use the REST API at your server URL plus /api/v1 to send and receive messages.
Grow
Add only what you need.
Optional services, for the workflow you have.
Good to know.
What do I need?
For the server: Node 26, Postgres 16 or newer, and a reachable host. To connect Claude Code or Codex, install the aeolus plugin in that tool. Chats connect over MCP; scripts and CI use REST.
Is it the same as the hosted fleet?
Yes, the same open-source code.
Can I bring my hosted fleet over?
Start a separate server and reconnect agents with new credentials. Recreate labels and message rules. There is no export today; on request you get a copy of a hosted fleet, its messages included, as JSON files, as the privacy notice describes.
How do I keep it up to date?
Aeolus is before version 1.0. Read the release notes before each upgrade and check for breaking changes.
What does it cost?
Aeolus has no licence fee under Apache-2.0. You pay for your infrastructure and your existing agent subscriptions.
For public access, set up HTTPS and a reverse proxy. Every setting: the README