Orchestration Watchdog Stop
Prompt
Safely identifies and dismisses the active orchestration watchdog session without touching worker sessions.
By Vedang Manerikar · prompts/orchestration-watchdog-stop.md · View source
What it does
When a multi-session run finishes, /orchestration-watchdog-stop resolves the exact watchdog session attached to the current coordinator (orchestration-watchdog-<master-id>) or validates an explicit session ID you pass.
It refuses to kill any session whose name does not start with orchestration-watchdog-, terminates the matching background PTY via interactive_shell, and confirms the watchdog has disappeared from both the PTY list and the pi-intercom roster.
When to reach for it
Invocation: Run /orchestration-watchdog-stop when your orchestrated run is complete.
- Wrapping up a multi-session run
- Stop the periodic wakeups cleanly while leaving any other background shells untouched.
What it adds
- /orchestration-watchdog-stop prompt template with prefix validation and dual PTY/intercom teardown checks.
Commands: /orchestration-watchdog-stop [watchdog-session-id]
How it fits
- Orchestration Watchdog — The teardown counterpart to /orchestration-watchdog.
- Pi Interactive Shell — Kills the background PTY session.
- Pi Intercom — Verifies the watchdog is no longer registered on the local intercom bus.
Good to know
- If multiple watchdogs are running and no argument is given, it stops only the one belonging to the current coordinator session and lists the others.
Source and setup
- Loaded via
prompts/orchestration-watchdog-stop.md- Attribution
- By Vedang Manerikar