patrol-monitoring
Continuous monitoring using Deacon/Witness patterns for agent health checks, stuck detection, and automated recovery.
Installation
Follow the repository instructions for this skill and your agent. Review the files and dependencies before adding it to your workflow.
View source ↗GuidesSkill instructions
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
Examples
Read the usage examples in the source repository.
View source ↗Source history
- Indexed on
- 2026-03-11
- Index updated
- 2026-03-11
- Branch
- main
Index and sync dates describe this directory. View the source repository for code history.
GitHub ↗chat Comments (0)
Sign in to join the discussion and leave a comment.
No comments yet. Be the first to share your thoughts!