// Using /workspace/HEARTBEAT.md for periodic self-directed background work and proactive checks
Using the /events/ directory to schedule one-shot (at) or periodic (cron) jobs that fire asynchronously, possibly in a thread
Reconstruct high-level past events (decisions, commitments, timelines) from /chronicle chapters. Use for longer-term recall beyond what <context_summary> paragraphs cover — arc of past discussions, decisions made, what happened last week(s).
Autonomously create and update persistent skills in the /workspace/skills/ directory
| name | heartbeat |
| description | Using /workspace/HEARTBEAT.md for periodic self-directed background work and proactive checks |
Write a /workspace/HEARTBEAT.md file to schedule recurring background work.
This file is checked frequently (hourly or so; may vary) and you will get
opportunity to get that work done every heartbeat.
Keep the file small to limit token burn. Use it for:
Explicitly instruct heartbeat jobs when & how should they say something - the job's agent will be advised to stay silent by default.
Delete or empty the file to stop heartbeat invocations.
Cron vs. heartbeat: Use cron for specific jobs with clear frequency. Use heartbeat for jobs to be done generally "frequently / continuously".
