wolf

Wolf — Cron Scheduler

The wolf is the lodge's scheduler. Each wolt owns its crons in its own wolt/wolf.json; the wolf scans every wolt every 30 seconds, and when a cron is due it starts a session for the owning wolt with the cron's message as the prompt, then sends a 🐺 notification.

Manage crons with woltspace wolf. It talks to the lodge, which validates everything before writing wolf.json, so a mistake comes back as an error instead of a cron that silently never fires.

Time zone

The wolf fires in the lodge machine's local time. 0 9 * * * means 09:00 on the clock of the machine the lodge runs on — no UTC conversion. woltspace wolf list prints the zone it is using, and every time it shows is in that zone. A container lodge runs on UTC unless its env file sets TZ; to choose the zone and move existing crons safely, see Time zone.

Add

The message (what the session is told to do) is read from stdin. Use a single-quoted heredoc so the shell leaves it alone:

woltspace wolf add --cron '0 9 * * 1-5' --notify telegram <<'WOLF_MSG'
Write today's standup notes from yesterday's commits.
WOLF_MSG

One-off, fires once at a lodge-local time and then removes itself:

woltspace wolf add --at 2026-03-22T14:30 <<'WOLF_MSG'
Check whether the deploy went through and tell jerpint.
WOLF_MSG

• --wolt defaults to you ($WOLTSPACE_WOLT_NAME); pass it to schedule for another wolt.
• --name defaults to the message's first few words (write-today-s-standup), made unique in that wolt.
• --notify telegram|slack also pings your human there when it runs ("🐺 woke up: " + session link). Leave it out and the wolf is quiet; the run still shows in woltspace wolf runs and on the lodge's wolves page. Slack needs SLACK_NOTIFY_CHANNEL set.
• --message TEXT instead of stdin for a one-liner.
• --dry-run shows the entry and the resulting file, writes nothing.
• --json on any command for machine-readable output.