Watchers

The daemon monitors the filesystem, git history, and runtime state through a set of watchers — each responsible for detecting a specific category of change and emitting signals into the routing pipeline. Watchers are the daemon's sensory layer: they normalize diverse sources of change into canonical signals, never performing work directly. Understanding which watchers exist and how they coordinate is essential for reasoning about what the daemon can see and react to.

Git Commit Watcher

Detects new commits on watched branches and emits signals that let agents react to code and configuration changes landed through git. Learn more

Job State Watcher

Monitors work item state transitions — created, running, succeeded, failed — and surfaces them as signals for downstream coordination and escalation. Learn more

Org Config Watcher

Watches .matic/ configuration files for changes to org settings, agent runtimes, channels, and plugins, triggering reloads or re-registration as needed. Learn more

Run Output Watcher

Observes output written by agent runs — logs, artifacts, and structured results — and emits signals that enable validation, chaining, and audit. Learn more

Signal Inbox Watcher

Monitors the staged signal directory and dead letter queue, ensuring inbound signals are picked up for routing and undeliverable signals are surfaced. Learn more

Watcher Registry

The central registry that tracks active watcher instances, manages their lifecycle, and provides the daemon with a single coordination point for startup, shutdown, and health checks. Learn more

Debounce and Coalescing

Strategies for collapsing rapid or duplicate filesystem events into single signals, preventing redundant work while preserving responsiveness. Learn more