Open-source personal AI OS

Maia OS

Your AI, your apps, your network.

One logical node is one brain and sovereignty domain. The JSON CLI is the current public client of the versioned protocol through @maia/sdk. Desktop, mobile, and web clients are planned or blocked source candidates and do not ship as product consumers today. Build is the planned complete user-facing ADE. Peer surfaces sit on that same node.

Foundation chain

Every product path is node, then versioned protocol, then @maia/sdk, then the built JSON CLI, then a real scenario. This site does not sit on that chain.

1. maia-node

   Durable local authority.

2. protocol

   Versioned schemas.

3. @maia/sdk

   Sole product-client facade.

4. maia CLI

   JSON-first built client.

5. scenario

   Real qualified evidence.

Surfaces over one node

These names organize client navigation. They are not independent backends, harnesses, or sources of truth.

Build

The planned complete user-facing ADE. Not a separate backend.

planned

Teammates

Durable Agents over the same node.

planned

Rooms

Human-agent collaboration context. Messages are not grants.

planned

Routines

Skill bindings with at most one optional trigger.

planned

Skill Studio

Author and review user-owned Skill revisions.

planned

Activity

Durable events, receipts, and audit projections.

planned

Advanced → Runtime Extensions

Higher-trust runtime-specific executable extensions.

planned

What exists today

The headless node, versioned protocol, @maia/sdk, and JSON CLI form the source-implemented candidate foundation. The first list is the complete source-callable current evidence. The second list is blocked and is not enabled. Neither list is implemented under the release-gated AGENTS meaning.

See the Node, Protocol, SDK, and CLI notes for the honest split. Product names live on Product Surfaces.