Skip to content
Maia OS

SDK

@maia/sdk is the only supported node-facing product-client boundary. Desktop, web, mobile, and the maia CLI consume it. Clients must not open a parallel node transport, read node storage, or supervise runtimes. This page is not an SDK reference. The SDK README owns exports and limits.

Source-implemented candidate — callable current evidence

The typed local-node client exposes these source-callable operations. They are not implemented under the release-gated AGENTS meaning and are not product enablement:

  • status and shutdown
  • project register, list, and show
  • workspace list, show, and explicit repository attachment
  • durable receipt lookup
  • probeRuntime for the Codex compatibility handshake
  • createSession, listSessions, showSession, and listSessionEvents

@maia/sdk/node is the first real adapter: explicit-endpoint or connectLocalNode discovery over the private descriptor, with private-file checks, one-MiB frames, eight in-flight requests, and a five-second deadline.

Source-implemented candidate — blocked

Exported and blocked. Not enabled:

  • startSession
  • sendTurn and showTurn
  • the 13 macOS live-terminal methods
  • the eight local-v1 orchestration methods

Observer attach/check/detach/resync, controller renew, restart, delete, and mutation reconcile remain unavailable or inert. The SDK never spawns Codex or a terminal.

Planned

Not present as enabled SDK operations:

  • showCurrentContext
  • remote HTTP/WSS transports
  • live subscriptions and cursor helpers beyond explicit page contracts
  • Skill, Teammate, Room, Routine, Runtime Extension, and Activity operations
  • Skill bundle recommendation, install, or sync

Unsupported

Browser, Expo, and mobile bundles must not import @maia/sdk/node. Windows runtime probing stays platform_unsupported until process-tree ownership is proven. No SDK method is implemented under the release-gated AGENTS meaning.

Next action

Read the SDK README, then the CLI notes. Installed discovery remains maia help --json.