@maiaos/node
Maia Node, the local authority of Maia OS: one process per machine and profile that owns Sessions, turns, worker accounts, durable state, event order and receipts for swarms of AI coding agents.
Pre-release. Maia publishes
canarybuilds to npm only, andlatestfollows the newest one (earlier nightly builds are historical). They are not release-qualified, and Maia has no stable release (D-202).
Requirements
- Node.js 24.22.1.
- macOS on Apple silicon or Linux x64, the platforms whose process host the
published builds ship (Linux is a source candidate). Windows is unsupported
and fails with
platform_unsupported. - On Linux, set pnpm's
packageImportMethodtoclone-or-copybefore you install: the Node refuses a process host with a second hard link, which pnpm makes on ext4. Worker containment also needs a delegated cgroup v2 subtree and Linux 6.12 or later (operations). - Claude Code or the Codex CLI, for workers.
Install
pnpm add -g @maiaos/node@canary
Install the maia CLI
with it to drive the Node.
Usage
Run the Node in the foreground, then check it from a second terminal with the CLI:
maia-node --desktop --profile <name> # --profile defaults to "default"
maia --profile <name> status # the Node reports ready
The Node binds an ephemeral port on 127.0.0.1 only and writes an
owner-private connection descriptor and credential to its profile directory.
Every client reaches it through @maiaos/sdk; none of them owns state.
From a source checkout, pnpm dev:node runs a Node inside an isolated dev
worktree and never touches your real ~/.maia. See the
quick start.
Status
Source candidate. The Node validates and authorizes each operation, stores
the result in SQLite, writes a receipt and runs Codex and Claude Code workers
as child processes under a native process host. On Linux,
maia-node remote install --local installs a managed background service on
this machine; other systems are planned. The
roadmap tracks each
slice.
Links
- Node architecture
- Operations: lifecycle, remote Nodes, SQLite, backup and observability
- Vendor executors
- Security policy
- Repository
In this section
- Harness boundaries
conversation/ is the shared durable-Session scheduler: one conversation per activation, serial turns, shared admission, recovery and exact interrupt settlement.
- Node telemetry
The Effect v4-native observability facade for Maia Node. It replaces the previous @vllnt/logger adapter; Maia does not retain that external dependency.
- Project metadata operations
The Project create/rename slice extends the existing Protocol → SDK → Node → CLI boundary. It does not add a renderer mutation path or an alternate database.
Imported from Maia OS docs at a2175bb