Schedules and heartbeats

Create a schedule

Schedules are local daemon jobs. They can save reports, notify Telegram, and use the global provider/model defaults unless overridden.

/schedule examples
/schedule add "daily 09:00" "Daily repo health" "Check git status, tests, dependencies, and security alerts."
/schedule list
/schedule run <id>

Agent-created schedules

The agent can use the permissioned schedule_list and schedule tools to create, update, pause, resume, delete, and list Libre Claw automations. It should use these instead of telling you to edit host cron, launchd, or systemd timers.

Create a schedule that sends me the Dinant weather forecast every day at 8am.

Dashboard controls

The dashboard can create, edit, pause, delete, and run one iteration immediately from the schedule card.

libre-claw daemon
open http://127.0.0.1:8766/dashboard

Hacker News brief

Fetch HN top/new stories, compare recent memory, and send only notable new AI, coding, infra, security, startup, and open-source stories.

Repo health check

Inspect git status, dependency updates, failing checks, and local test risk before the day starts.

Server monitor

Check weather alerts, power outages, reachability, and local incident sources for a remote server site.

Heartbeats

Heartbeats are lightweight recurring check-ins for “keep an eye on this” tasks.

/heartbeat status
/heartbeat start every 30 minutes
/heartbeat once
/heartbeat stop

Report quality

For scheduled reports, write prompts that demand a final concise report and ask the model to hide process narration.

Fetch Hacker News top/new stories, compare recent memory, and send only new notable stories. Include title, link, score/comments, and one sentence on why it matters. Keep it under 8 bullets.