Skip to content
Maia OS

Node

@maia/node is the headless authority. One logical node is one brain and sovereignty domain. Clients authenticate to it and keep cache-backed views. This page is presentation only. The Node README and architecture remain authoritative.

Source-implemented candidate — callable current evidence

These exist as documented public foundations of the desktop-local node. They are source-callable current evidence, not product enablement:

  • maia-node --desktop single-profile lock and authenticated user-local IPC
  • readiness, node.status, idempotent node.shutdown, and bounded drain
  • versioned SQLite command/event storage and bounded file-configuration writes
  • project, repository, workspace, and receipt records
  • runtime.probe Codex compatibility handshake
  • session.create, session.list, session.show, and session.events.list

The node opens no TCP listener. maia-node --background and maia-node serve remain rejected. Node 24.19.0 is the only supported JavaScript runtime.

Source-implemented candidate — blocked

Source exists. Named qualification gates remain. These are not enabled product behavior:

  • session.start Codex activation and exact-thread resume
  • turn.send / turn.show
  • macOS live-terminal create/list/show/events/read, controller request/show/acquire/release, input write, resize/signal/close
  • local-v1 orchestration Run/inbox/question/settle subset
  • harness.installed.list four-item catalog read
  • macOS ProcessResourceManager integration and the compact node.status resource projection

Unavailable or inert terminal surfaces include observer attach/check/detach/resync, controller renew, restart, delete, and reconcile.

Planned

Accepted or proposed, with no public product claim:

  • structured Session attachments, approvals, steering, and interruption
  • authenticated Invocation context and maia context show
  • client NodeDirectory, multi-node switch, NodeBootstrap, and remote pairing
  • device-capability hosts, grants, and native invocation receipts
  • background OS-service and remote node modes

Unsupported

  • Windows process-tree ownership. runtime.probe returns platform_unsupported there until lifetime ownership is proven.
  • Windows live terminal. The terminal candidate is macOS-first.

Next action

Read the Node README, then the Protocol, SDK, and CLI notes. Delivery order lives in the node roadmap.