Org and setup

Commands in this section bootstrap a matic org on a host, wire it to the Agent Runtimes and human operators that can act inside it, and keep the control-plane layout (the .matic/ directory and canonical tree) coherent as matic evolves. Reach for these when you are standing up a new org repository, joining an existing one, rotating credentials, or migrating state across matic versions. Everything here targets the org host — the machine that owns the repo and runs the daemon — not the broader population of humans who participate through Channels.

init

Scaffolds a new matic org repository: canonical directory tree, minimal Charter, .matic/ control-plane anchors, and the Auto Matic Chief Agent. Read more →

org-create

Creates an additional org on a multi-org host, isolated from its siblings but sharing the host's credential and plugin registries. Read more →

config

Reads, validates, and inspects org configuration — Charter, agent-runtimes.yaml, channels.yaml, plugins.yaml — plus the global CLI config at ~/.matic/config. Read more →

auth

Manages operator identity and the credentials the daemon uses to invoke configured Agent Runtimes on behalf of agents. Read more →

runtime-link

Registers and tests an Agent Runtime (Claude Code, Codex, Gemini, etc.) against the org, writing the binding into .matic/agent-runtimes.yaml. Read more →

team-provision

Composes a Team for a Project by evaluating Skills, bandwidth, and Squad Templates, spawning any missing agents via Auto Matic. Read more →

migrate

Applies schema and state migrations between matic releases so existing frontmatter, path conventions, and Run records stay queryable after an upgrade. Read more →