Your agents ask. You answer from anywhere.
When an agent needs a decision, it asks with options and a recommendation. You choose; it carries on.
- 05:00reviewer → you · Harbour's unit or your setting?waits for you
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.
Options, context, and a recommendation.
A title, the context, numbered options, and the one the agent would pick, with why.
Should depths follow the harbour's unit or the user's setting?
Dover publishes metres and some American harbours feet. The app has a units setting nobody uses.
Every open question in one list.
The Questions page holds every open decision, with a count in the navigation. On desktop or phone.
Pick one, add a note, done.
Or send a note alone when none fits. Your answer goes back to the agent as a reply, a message like any other.
Should depths follow the harbour's unit or the user's setting?
reply to reviewer: 1. The harbour's unit · reviewer: Idle → Working
| Where your agent runs | When you answer |
|---|---|
| Claude Code on your machine | Its session wakes and gets your answer |
| Claude Code on the web | Its session wakes while its container runs, at the cost of one turn about every 2 hours |
| Codex, desktop or CLI | Your answer is passed into its task |
| Codex Cloud, ChatGPT, a Claude chat | Your answer waits until you return to that chat |
| A session that was closed | Your answer waits in the agent's ship until it reconnects. The optional trierarch, a local session launcher, can start its next coding session |
For supported coding sessions, the plugin watches for your reply without spending model tokens. Aeolus delivers your answer; the agent decides what to do next.
A decision that can wait.
An unanswered question stays open until you answer, or its agent withdraws or replaces it. Stale means withdrawn or replaced, not expired.
Drop offline tide tables after a month, or after a season?
Replaced byDrop offline tide tables after a season?
| State | What it means | Can you answer it? |
|---|---|---|
| Open | Waiting for your answer | Yes |
| Answered | You answered. Your answer shows with it | No, it is closed |
| Stale: withdrawn | The agent took it back before you answered | No |
| Stale: replaced | The agent asked a newer version. It links to the new one | No, answer the new one |
Good to know.
Will my agents know how to ask?
Claude Code and Codex ask through the aeolus plugin. Chats over MCP and your own code over REST can ask too.
Will I get a notification?
Not yet. Questions wait in the console, with the count in the navigation. Open it on your phone when you have a moment.
What if none of the options fits?
Send a note alone. The agent gets it as your answer.
Do my other agents stop while one waits?
No. Only the agent that asked waits on you. The others keep working.
What does it cost me to try?
A few minutes. The live demo needs no account, a hosted fleet is free during early access, and running your own is open source.
What works today, and its limits: the README