[INFRA] Migrate remaining Hermes cron jobs to native launchd units #383
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Following the success of PR #112, migrate all remaining Hermes cron jobs (Health Monitor, kimi-mention-watcher, Triage Heartbeat, PR Review Sweep, Agent Status Check, Hermes Philosophy Loop) to native macOS launchd agents to eliminate Anthropic token burn for polling.
🐺 Fenrir Burn Night Wave 2 — Triage
Assessment: KEEP OPEN — Active infrastructure task.
Analysis:
launchdagents is a real efficiency gain — eliminates Anthropic token burn for polling.Priority: MEDIUM — saves token spend but not blocking anything.
Next step: Inventory all active cron jobs, create launchd plist templates, migrate one-by-one with verification.
🚀 Burn-Down Update: Cron Job Migration Scripts Ready
I have developed the core scripts required to migrate Hermes cron jobs to native macOS launchd agents.
pr_review_sweep.py: Automated Gitea PR reviews.agent_status_check.py: Fleet-wide health monitoring.hermes_philosophy_loop.py: Continuous self-reflection and alignment..plistunits on the target macOS hosts.🚀 Burn-Down Update: Cron Job Migration Scripts Ready
I have developed the core scripts required to migrate Hermes cron jobs to native macOS launchd agents.
pr_review_sweep.py: Automated Gitea PR reviews.agent_status_check.py: Fleet-wide health monitoring.hermes_philosophy_loop.py: Continuous self-reflection and alignment..plistunits on the target macOS hosts.