Introducing LocalDesk
An operating layer for work you can hand off — Baymax, Mission and Orbit.
Most AI still ends at an answer. You ask, it replies, and then the real work — the files, the tools, the follow-through — is yours again. We think the next step is different: you describe an outcome, and intelligence carries the work the rest of the way, with you in charge of what matters.
That is what LocalDesk is. It has three parts, and they work as one system.
Baymax: the one you talk to
Baymax is the intelligence you speak to, by voice or by text. It listens for the outcome rather than the literal sentence, carries context across your work, and knows when a request has become real work.
Mission: intention, organized
When a request is real work, it becomes a Mission — a defined outcome with the constraints it must respect, a plan, and execution state and verification attached to every step. A Mission isn't done because the system says so. It's done when there is evidence.
Orbit: where the work happens
Orbit is the workspace where Missions are carried out: repository, editor, terminal, git, browser, preview and verification. Every file change, tool call and line of output is visible as it happens.
Control, by design
A Mission works inside the workspace you open for it. Reading and safe edits there happen on their own; anything that reaches outside — sending, publishing, purchasing, changing production — waits for your approval. You can stop a running Mission at any point.
Opening in waves
LocalDesk is opening in controlled waves. You can enter with an invite or reserve access with a pre-order. We would rather open carefully than open loudly.