Babysitter patrol-monitoring
Continuous monitoring using Deacon/Witness patterns for agent health checks, stuck detection, and automated recovery.
install
source · Clone the upstream repo
git clone https://github.com/a5c-ai/babysitter
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/a5c-ai/babysitter "$T" && mkdir -p ~/.claude/skills && cp -r "$T/library/methodologies/gastown/skills/patrol-monitoring" ~/.claude/skills/a5c-ai-babysitter-patrol-monitoring && rm -rf "$T"
manifest:
library/methodologies/gastown/skills/patrol-monitoring/SKILL.mdsource content
Patrol Monitoring
Overview
Continuous monitoring using Gas Town's Deacon/Witness pattern. The Deacon supervises overall health, the Witness manages per-rig agent lifecycle, and the Boot (Dog) watches the Deacon itself.
When to Use
- During active convoy execution
- When agents may become stuck or unresponsive
- For long-running multi-agent workflows
- When automated recovery is desired
Process
- Health check all active agents and convoys
- Detect stuck or unresponsive agents via heartbeats
- Recover - restart, reassign, or escalate as needed
- Report patrol findings with trend analysis
Monitoring Roles
- Deacon: Daemon supervisor, monitors overall health
- Witness: Per-rig lifecycle manager for workers
- Boot (Dog): Watches the Deacon every 5 minutes
Recovery Modes
- restart: Restart the stuck agent session
- reassign: Move beads to a different agent
- escalate: Alert human for manual intervention
Tool Use
Invoke via babysitter process:
methodologies/gastown/gastown-patrol