heartbeat-watchdog

You can monitor WezTerm panes by referencing their id or name to trigger periodic heartbeats and runtime logs. The observer tracks live pane activity and emits status updates at fixed polling intervals without embedding transport logic.

Yes, you can observe JSONL session logs generated by Codex, Claude, or Pi style workflows. The watchdog tails these logs and emits heartbeat intervals to track ongoing session activity and status changes.

Monitoring glob-based file sets involves applying the observer to a file pattern to track changes and activity. The watchdog emits periodic heartbeat logs and exposes tail views for the matched files at your chosen fixed interval.

Yes, the observer supports multiple source mappings, allowing you to monitor WezTerm panes, single files, glob-based sets, and JSONL logs concurrently. Each source runs with fixed-interval polling and optional lightweight notifications.

You can use the watchdog's simple stop controls to halt the observation session. It exposes runtime logs, status views, and tail outputs so you can review the captured activity before terminating the heartbeat polling.

Yes, the watchdog provides a lightweight notification path for optional alerts. It handles the observation and heartbeat emission while keeping the transport logic external, so you receive status updates without modifying the core observer.