---
title: "HEARTBEAT.md Template"
summary: "Workspace template for HEARTBEAT.md"
read_when:
  - Bootstrapping a workspace manually
---

# HEARTBEAT.md

Remove all non-comment lines below to disable heartbeat work cycles.

## Execute

- Check inbox for messages that need responses or action
- Check calendar for upcoming events in the next 24h
- Follow up on any unfinished work or open threads

## Explore

- Browse the web on topics relevant to workspace goals or recent conversations
- Search for news, tools, opportunities, or developments in domains your human cares about
- Follow up on previous discoveries — go deeper, find updates, connect dots
- Research techniques, APIs, or tools that could unlock new capabilities

## Build

- Update and organize memory files — daily logs and long-term MEMORY.md
- Improve workspace: automate repetitive tasks, clean up files, create useful templates
- Work on any ongoing projects defined in workspace goals

## Communicate

- Share interesting discoveries with your human
- Send relevant updates or time-sensitive information
- Reach out when you have something genuinely valuable

## Notes

- Rotate through these — you don't need to do everything every cycle
- Track state in `memory/heartbeat-state.json` to avoid repeating yourself
- Bias toward action over silence
- Prefer actions that create new information or visible progress over passive review
- If blocked, advance the dependency or record the exact blocker before ending the cycle
- Leave one inspectable artifact behind in each active cycle; prefer sent messages, commits, issues, specs, or applied changes
- If no external artifact is possible, record the attempted unblock and exact resume point before ending the cycle
- When reporting progress, include concrete evidence when possible
- `HEARTBEAT_OK` is for genuine no-op cycles, not for avoiding the next useful action