CLI

The matic command is the primary operator interface for bootstrapping, inspecting, and orchestrating an org. The CLI is deliberately thin — all runtime capability lives in packages, with the CLI providing entry points, argument parsing, and output formatting. Commands split across two execution paths: read-only operations resolve directly against the filesystem, while execution and live-state commands route through IPC to the Daemon. This split means operators always have visibility into org state, even when the Daemon is down.

Command Envelope

The request/response structure that wraps every CLI invocation — argument validation, scope resolution, error contracts, and the execution-vs-inspection boundary that prevents accidental mutation from read paths. Read more

Namespace Registry

How command namespaces map one-to-one to matic primitives (agents, projects, work-items, runs, decisions, risks, etc.), the handle convention shared across all namespaces, and scope inference from the current working directory. Read more

Quickstart Flow

The matic quickstart command — a single entry point that scaffolds an org, starts the Daemon, and drops the operator into a chat session, turning a bare directory into a running org in one step. Read more

IPC Client

The Unix socket transport between CLI and Daemon at .matic/daemon.sock — typed request/response framing, connection lifecycle, cross-process error propagation, and compatibility negotiation. Read more

Graceful Degradation

Which commands work without a running Daemon and why. Read-only commands (list, show, status) resolve from the filesystem directly; execution commands surface a clear error with a recovery hint pointing to matic daemon start. Read more

Output Formatting

The terminal output layer — tables, trees, status badges, spinners, and the error renderer that turns structured failures into human-readable messages with actionable recovery steps. Read more

Terminal Chat

The interactive chat channel that runs in-process with the CLI, connecting to the Daemon over IPC for signal routing and agent response delivery. Covers session management, @mention routing, multi-agent collaboration, context injection, and turn rendering. Read more