
Install Watchdog
Install a launchd or systemd watchdog so egregore autonomously relaunches agent sessions on your Mac or Linux machine.
Install
npx skills add https://github.com/athola/claude-night-market --skill install-watchdogWhat is this skill?
- macOS path: install_launchd.sh → ~/Library/LaunchAgents/com.egregore.watchdog.plist on a 300-second interval
- Linux path: install_systemd.sh for an equivalent systemd watchdog unit
- Watchdog checks running session, budget cooldown, and active manifest work items before relaunch
- Explicitly not for CI/CD runners—use the orchestrator directly there
Adoption & trust: 1 installs on skills.sh; 304 GitHub stars; 0/3 security scanners passed (skills.sh audits); trending (+100% hot-view momentum).
Recommended Skills
Azure Kubernetesmicrosoft/azure-skills
Github Actions Docsxixu-me/skills
Deploy To Vercelvercel-labs/agent-skills
Vercel Cli With Tokensvercel-labs/agent-skills
Turborepovercel/turborepo
Docker Expertsickn33/antigravity-awesome-skills
Journey fit
Primary fit
Persistent OS daemons and relaunch policy belong in Operate—keeping an agent orchestrator alive in production-like local infra. Maps to infra: native schedulers (launchd/systemd), plist/unit files, and five-minute health checks before spawning sessions.
Common Questions / FAQ
Is Install Watchdog safe to install?
skills.sh reports 0 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.
SKILL.md
READMESKILL.md - Install Watchdog
# Install Watchdog ## Overview Installs a persistent daemon that monitors the egregore process and relaunches it when needed. The daemon uses the OS-native scheduler (launchd on macOS, systemd on Linux) to run a watchdog script every 5 minutes. The watchdog script checks: - Whether an egregore session is already running. - Whether the budget is in cooldown. - Whether there are active work items in the manifest. If all conditions are met, it launches a new egregore session. ## When To Use - After initializing an egregore project (`egregore init`) when you want autonomous relaunching. - When setting up egregore on a new machine. ## When NOT To Use - On CI/CD runners (use the orchestrator directly). - When you want manual control over session launches. ## Installation Steps ### 1. Detect the operating system ```bash OS=$(uname -s) ``` ### 2. Run the appropriate installer **macOS (launchd):** ```bash bash plugins/egregore/scripts/install_launchd.sh ``` This script creates a plist at `~/Library/LaunchAgents/com.egregore.watchdog.plist` that runs the watchdog script every 300 seconds (5 minutes). **Linux (systemd):** ```bash bash plugins/egregore/scripts/install_systemd.sh ``` This script creates a systemd timer and service unit at `~/.config/systemd/user/` that fires every 5 minutes. ### 3. Verify installation **macOS:** ```bash launchctl list | grep egregore ``` Expected output: a line containing `com.egregore.watchdog` with a PID or `-` status. **Linux:** ```bash systemctl --user status egregore-watchdog.timer ``` Expected output: `active (waiting)` status. ### 4. Confirm to the user Report the installation result, the schedule interval, and the log file location: - macOS: `~/.egregore/watchdog.log` - Linux: `journalctl --user -u egregore-watchdog` ## Uninstall Command To remove the watchdog, run: ``` Skill(egregore:uninstall-watchdog) ``` Or invoke the uninstall skill directly via the command `/egregore:uninstall-watchdog`. ## Troubleshooting - **Permission denied on plist**: ensure the script runs as the current user, not root. - **systemd user session not available**: run `loginctl enable-linger $USER` to enable user services without an active login session. - **Watchdog not firing**: check the log output and verify the scheduler is loaded (`launchctl list` or `systemctl --user list-timers`).