// 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).
Using the /events/ directory to schedule one-shot (at) or periodic (cron) jobs that fire asynchronously, possibly in a thread
Using /workspace/HEARTBEAT.md for periodic self-directed background work and proactive checks
Autonomously create and update persistent skills in the /workspace/skills/ directory
| name | chronicle-read |
| description | 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). |
Chronicle files in /chronicle/ (read-only, auto-maintained) are numbered chapter files (000001.md, 000002.md, etc.) with YAML frontmatter and timestamped narrative paragraphs:
---
openedAt: "2026-02-20T14:30:00Z"
closedAt: "2026-02-21T10:15:00Z"
summary: "Brief summary of the chapter."
---
[2026-02-20T14:30] First paragraph content.
[2026-02-20T14:35] Second paragraph content.
<context_summary> messagesclosedAt absent = current (open) chaptersummary: lines across chapters to find relevant periodsread /chronicle/NNNNNN.md for full chapter content/chat_history/ chatter