First-Party Plugins

First-party plugins ship with matic and cover the integrations an operational org needs on day one: human approvals, cost guards, notifications, archetype distribution, git side effects, and signal transport. They are built against the same manifest, lifecycle, and isolation contracts as third-party plugins — nothing privileged — so their source doubles as the canonical reference for authors writing their own. Each plugin in this section is installable per-org, declares its capabilities explicitly, and runs subprocess-isolated from the daemon.

Overview

What ships in the box, how first-party plugins are versioned and released, and when to prefer a bundled plugin over a custom one.

Approval Gate

Blocks risky steps at HITL checkpoints until a designated operator or owner approves — the reference implementation of pause-state semantics for governed runs.

Archetype Sync

Distributes Archetype definitions across orgs and repos, keeping agent blueprints, Skills, and Probe defaults aligned with an upstream source of truth.

Cost Sentinel

Watches token and tool-call spend against per-run and per-org budgets, emitting warning signals and halting dispatch before limits are breached.

Git Hooks

Wires matic into repository-side events — pre-commit, post-merge, worktree transitions — so git activity becomes Signal input and runs can write back through sanctioned hooks.

Signal Relay

Forwards Signals between orgs, daemons, and external transports, letting a Signal raised in one scope fan out or route to the agent that should handle it.

Slack Notifier

Delivers Notifications and HITL prompts into Slack channels and DMs, closing the loop between autonomous runs and the humans who need to react to them.