AERIS OS runs several agents at the same time on separate lanes of one project, with every lane followed from one orchestration hub. Every agent reads from AERIS STORM, a shared second brain of your projects, conversations and decisions.
Three agents, one feature, no copy-paste
You get one reviewed result without carrying context between tools.
Live demo
Claude plans the interface, Codex builds it and Hermes reviews it, all at once, from the same project and the same memory.
Say thisPlan the settings screen with Claude, have Codex build it, and get Hermes to review it before I see it.
What runs on its own
Each lane keeps working in parallel and reports back to the hub.
The runtime hits its limit, the work doesn't stop
Your work keeps moving when one runtime runs out of usage.
Live demo
AERIS OS routes across your runtimes automatically by your rules, so a job that hits one runtime's limit continues on another.
Say thisIf Claude runs out, move this to Codex and keep going.
What runs on its own
Routing follows the rules you set, without you opening a new chat.
Why did we decide that?
You can find a decision again instead of scrolling back through chat.
Live demo
AERIS STORM records your sessions, turns conversations into context and decisions into knowledge. Open a decision and see the project and conversation it came from.
Say thisWhat did we decide about the pricing table last month, and why?
What runs on its own
Every agent on AERIS OS reads the same foundation, so the next agent already knows it. Stored knowledge stays on your devices.
Mission View: the whole crew on one screen
You manage the work, not the windows.
Live demo
Stay close to one task and see its activity, changes and next step, or zoom out to Mission View and see every agent's lane.
Say thisShow me every lane that's blocked.
What runs on its own
Lanes keep moving toward one outcome while you watch from the hub.
Let your agent install the desk, then plug in your tools
You get a checked install of AERIS OS on Windows 10/11 or Linux, connected to the tools you already use, and the sign-in stays with you.
Live demo
Your agent follows a plain-text runbook, checks the SHA-256 checksum before installing anything, then hands the sign-in back to you. AERIS OS connects to external MCP servers over stdio or HTTP, and runs its own MCP server with tools such as msg_send, task_create and session_search.
Say thisPlease install AERIS OS by E:mergence from emergencerising.com/aerisOS.
What runs on its own
The checksum check and install run on their own; only the sign-in waits for you. Once installed, your agents can call AERIS OS tools through its MCP server.