Watchers

Watchers observe agent sessions and project activity so Codifix can capture useful context without requiring every fact to be manually entered.

Watcher manager

The recommended path for Codex-linked sessions. The manager detects live sessions, maps them to projects, and starts a watcher automatically.

With knowledge areas configured, the manager resolves each repository against the operator-owned routing policy and pins the child's exact area, instance and configuration. Invalid or removed routes stop that child; they do not redirect captures into General. See Area routing.

codifix watcher manager enable
codifix watcher manager status

Manual / generic watcher

For agents or environments where the manager doesn't apply, run a watcher directly:

codifix watcher run    --project <slug>
codifix watcher status --project <slug>

Foreground watchers observe repository changes, debounce bursts, and send activity to the selected service. Use an explicit area when required. Legacy per-project watcher enable is rejected for area deployments; use the manager and the operator's coordinated watcher procedure.

Lifecycle

Watchers move through health states with automatic recovery:

A healthy watcher sends periodic heartbeats. If heartbeats stop, the watcher becomes Stale. The manager attempts a restart before marking it Failed.

Verify

codifix status     --project <slug>     # combined service, watcher, MCP, and doctor status
codifix activities --project <slug> --kind watcher --limit 10

Open the TUI Watchers tab to see live watcher state, or the Activity tab to inspect captured events.

Next

Read Agents, MCP, or How it works.