Skip to main content
Monosystem is the transport and auth-owner CLI for the Monolex machine estate. It starts local headless servers, maintains the niiad gateway daemon, manages registered devices, controls live remote machines through session.monolex.ai, transfers home-confined files, and synchronizes a PTY result mailbox. Published contract: monosystem 0.3.21, OpenCLIs build 2026-07-15-182726. The executing binary, registry, and public CDN metadata agree on this release. Registry ownership: the canonical docs_url is this page, the public product homepage is https://monolex.ai, and Monosystem pairs with NIIA, VPNCLI, OpenCLIs, OpenCLIs Vault, Monolex Headless, and Monopty. Repository ownership remains monolex/monolex; no public source URL is advertised while that repository is private. Version 0.3.21 adds plan-first, exactly scoped remote OpenCLIs updates and a per-device high-risk command gate. It preserves the auth-owner, headless, presence, file-transfer, and mailbox boundaries from 0.3.20.

Quick Start

Since the M1 auth migration, monosystem login owns estate authentication and writes the shared vault JWT read by the other estate binaries.

Authentication and Devices

Headless and Daemon Lifecycle

serve also accepts --device-id, --app-id, --cols, --rows, and --proxy. Default app id is default, and it must match the running PTY daemon. On Windows, daemon start validates and mirrors the existing vault AES keys before installing its S4U Scheduled Task. The task receives a Windows-native PATH and file-storage mode without putting tokens in argv or environment. Startup succeeds only after one live daemon PID passes consecutive readiness probes; missing keys, a mismatched mirror, or an accepted task that exits early returns non-zero and names niiad-service.log.

Remote Commands

Targets must be an exact machine name, exact alias, or dev:<device-id>. Partial and ambiguous matches fail. Relative and ~/... receiver paths resolve below the receiver home; absolute paths are accepted only below that home. Traversal and symlink escape attempts are denied.
The frame relay does not turn relay handles into typed PTY ids. Use Monopty locally on the target or authenticated SSH when exact session inventory and history are required.

Scoped Remote Update Contract

The receiver always plans first. It stops and restores Headless only when monolex-headless is selected, and schedules its own daemon restart only after a successful monosystem self-update. Updating an unrelated tool interrupts neither runtime. Plan, child, restart, protocol, and 600-second terminal-ACK timeout failures return non-zero. The dry-run path neither installs nor requires the mutation gate.

Mailbox and MCP

Typed MCP Command Map

monosystem --mcp-schema exposes 34 non-recursive command shapes. Service startup, login/logout, and the MCP server itself remain CLI lifecycle surfaces rather than recursively exposed MCP tools.

Relationships