Applications
Applications are replaceable clients of Maia's protocol. They do not own durable control-plane truth.
cli— reference client and first complete product surface.client— one shared Expo product application for the Tauri-hosted Desktop renderer and native iOS/Android builds.desktop— macOS-first Tauri packaging and narrow native boundary.
Desktop is the first graphical product. Mobile follows from the same
apps/client application. There is no standalone web control application: the
Expo web export is local Tauri content and a headless test artifact. Expo Go is
not a product or qualification target.
Business mutations must use the protocol registry rather than direct UI,
Tauri, Expo, voice, or agent-extension handlers. The complete voice-first,
single-cockpit, infinite Swarm Canvas, streaming, mobile, and qualification
contract is in
docs/clients/architecture.md. See also
architecture and roadmap.
In this section
- @maiaos/cli
The maia command-line tool and MCP server for Maia OS: start, drive, observe and stop swarms of AI coding agents (Claude Code and Codex workers) from a terminal, a script or another agent.
- Maia client (@maiaos/client)
Status: source candidate, not release-qualified. The shared Expo application for Maia OS: one React Native codebase that renders Maia Node state for the Tauri desktop app today and native iOS and…
- Maia Desktop (@maiaos/desktop)
Status: source candidate, macOS first and Linux second. The Maia OS desktop app: a Tauri v2 shell that hosts the shared Expo client, so you can watch and steer your swarm of AI coding agents (Claude…
Imported from Maia OS docs at a2175bb