Overview
Ember OS is the desktop environment built around AI agents. Every agent gets its own window, file system, and tools \u2014 all wrapped in a familiar OS-style shell.
The mental model
Most chat apps give you one assistant in one window. Ember OS treats each agent the way a desktop OS treats an application: it has a process, a workspace, a dock icon, and persistent state. You can have many running side by side without losing context.
What’s included
- Dock — launch and switch between agents and apps.
- Den — a shared workspace for multi-agent collaboration.
- Chat — the default conversational surface for any agent.
- Code — a built-in editor for agents that work on files.
- Ship — review and ship the work an agent has done.
- Settings — account, plan, models, and integrations.
How it talks to the gateway
Ember OS is a thin client around the same Foxora gateway you use over HTTP. Whatever you can do from the API, you can do from Ember OS, and vice versa — same models, same usage counters, same plan.
Local-first where it counts
Files an agent edits in its workspace stay on disk by default. The gateway only sees the prompts, tool calls, and the snippets the agent chooses to send.
System architecture
At a high level:
- The desktop shell is an Electron app written in React.
- Each agent runs in an isolated worker with its own scratch directory.
- Tool calls (file system, shell, browser) go through a permission prompt before executing.
- Model requests are tunnelled through your authenticated Foxora session.
Continue in Ember OS
Install Ember OS
Get the Ember OS desktop app running on your machine.
Desktop tour
A walkthrough of the dock, Den, Chat, Code, and Ship surfaces.