watch

You can monitor subprocess output by running background watches that emit conversation notifications from subprocess streams. This enables real-time awareness of system events without manual polling during active project sessions.

Configured watches auto-register enabled monitors at session start, maintaining a runtime registry. This ensures your background monitoring setup persists and initializes automatically across ongoing project sessions.

Background watches handle state management by storing a runtime registry that persists across sessions. The registry logs status to the shell transcript and ensures each event line becomes a tracked notification.

The best way to monitor logs and streams is using ad-hoc watches to start on demand for specific commands, or configured watches for continuous observation. Each event line surfaces as a real-time conversation notification.

Manual polling is not needed because background watches continuously observe system events and surface alerts in real time. The monitors emit conversation notifications directly from subprocess outputs, keeping you informed automatically.

A runtime registry enforces a deterministic workflow for background monitoring by tracking active watches and storing state. It supports both ad-hoc and config-based watches, ensuring consistent monitoring and notification delivery across sessions.