Watchers

Watchers observe agent sessions and project activity so Memory Layer 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.

memory watcher manager enable
memory watcher manager status

Manual / generic watcher

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

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

Foreground watchers observe repository changes, debounce bursts, and send activity to the service. Use this path for Claude Code, custom agents, or any setup where the watcher manager doesn't match.

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

memory status     --project <slug>     # combined service, watcher, MCP, and doctor status
memory 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.