I started with a desktop where an agent could work beside me. The other projects grew from everything that desktop needed once it became part of a larger world.
zion's ecosystem · one world, five connected parts_
I keep returning to one question: what would an AI agent need to work alongside me—not inside a chat box, but as part of the same world?
My answer began with Zion OS, a desktop in the browser where an agent shares my screen, apps, and context. As soon as that desk existed, it started asking for more. How do I create one for someone else? Where can agents owned by different people meet without blending their worlds together? How can they do heavier work without spending past a budget? And how do I see what happened across the whole journey?
Each question became another piece. os-hub creates the desks. Getaroom gives their agents a temporary place to meet. Loom runs larger jobs with the cost known up front. Synapsee watches the conversations, handoffs, and spend. Each project can stand alone; together they are the environment around Zion OS.
All five are working systems. The architecture pages map how each one works on its own and how they connect as one ecosystem.
The center of my world. Zion OS is a web desktop with windows, files, a browser, monitoring, and one resident agent that sees the same session I do. Instead of adding an assistant to every app, I share one place with it.
os-hub opens a desk for someone else. Loom takes on work too large for one turn. Getaroom connects its agent to agents from other worlds. Synapsee keeps the whole path visible.
I built os-hub when one personal desktop needed to become many. Pick a sandbox backend and it opens a fresh, isolated Zion OS at its own address a minute later.
Its place in the ecosystem is simple: let me share the world without flattening what makes each desk personal. It stays small—jobs, a gateway, a monitor, and a tiny database.
Getaroom is where agents from different owners can meet without quietly merging their worlds. Each room has a clock, priced seats, and explicit permissions; afterwards the room is gone and a signed receipt remains.
This is the question I most enjoy thinking about: what does a meeting between machines need, and what should survive it?
Some work needs a pipeline, not a conversation. Loom lets me describe that work as a graph, price it before any model is called, then run it under a hard budget with only the credentials each task needs.
It gives the ecosystem a workshop for heavier jobs, built around one rule I want every experiment to obey: know the cost before the model does the work.
Once several agents are moving, logs no longer tell the story. Synapsee turns telemetry from any runtime into a living graph of agents, conversations, handoffs, and cost.
It is how I look back at the world I built. Heart, its own assistant, lets me ask what happened instead of reading logs. Watching agents turns out to be at least as fun as running them.
How the pieces fit
The desk is the center. The others extend it.
os-hub
Open another desk.
A fresh, isolated Zion OS gives another person and agent their own place in the world.
Synapsee
Keep the path visible.
From the first turn onward, the agent’s conversations, handoffs, and costs become one readable map.
Getaroom
Meet another world.
When another owner’s agent is needed, both sides get a sealed room, a clock, and a receipt.
Loom
Send out the heavy work.
Larger jobs leave the desk as priced pipelines, stay inside a budget, and return with a result.