Local-first automation watchdog
Know when critical automation silently fails.
Honeycron finds and watches the scripts, schedules, and jobs your product depends on—then gives you one digest explaining what broke, why, and what to do next.
Runs locally. No hosted account or scheduler migration required.
openclaw-cron-health
Last passed yesterday at 09:00
Likely cause
Enabled cron still reports a stale error state.
Next action
Inspect Clubpicks Weekly Prize Money Setup and rerun its health check.
Operator signal
From silent failure to a clear next action.
Honeycron groups repeated failures, keeps the last known success visible, and points the operator toward recovery instead of adding another stream of raw logs.
- See when a job last passed
- Recognize repeated failure streaks
- Get a likely cause and recovery step
openclaw-cron-health
Last passed yesterday at 09:00
Likely cause
Enabled cron still reports a stale error state.
Next action
Inspect Clubpicks Weekly Prize Money Setup and rerun its health check.
Why it matters
The same failure repeated after the last known success, so Honeycron keeps it in the current failure inbox.
How it works
Observe the workflow you already have.
Honeycron is a reliability layer, not another workflow engine. Start from a repo and add watches only where failure would matter.
honey doctorDiscover what matters
Honeycron scans a repo for scripts, schedules, workflows, and monitoring gaps.
honey watchWatch it where it runs
Wrap the critical commands without moving execution, secrets, or logs into a hosted scheduler.
honey digestAct on one clear signal
See the last success, repeated failures, likely cause, and the next recovery action.
Local by default
Reliability without moving the work.
No migration
Keep using cron, GitHub Actions, Vercel, launchd, and the scripts you already trust.
Secrets stay local
Commands run on your machine and the local run ledger is redacted by default.
One operator view
Inspect scattered automation through one run ledger, digest, and local cockpit.
Quickstart
Inspect your first repo locally.
Clone Honeycron, install its dependencies, and run the scanner. honey doctor only inspects the repository and suggests watches; it does not start a daemon or hosted sync.
$ git clone https://github.com/mmcm77/honeycron.git
$ cd honeycron
$ npm install
$ node ./bin/honeycron.mjs doctorEarly access
Map the automation keeping your product alive.
The local CLI works today. Honeycron is looking for operators who want to test it against real scripts, schedules, and failure modes before hosted sync is built.