// 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).
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 | manage-async-jobs |
| description | Using the /events/ directory to schedule one-shot (at) or periodic (cron) jobs that fire asynchronously, possibly in a thread |
Create JSON files in /events/, use unique filenames.
{"type": "one-shot", "text": "Remind to go to sleep early", "at": "2026-02-26T23:00:00+01:00"}
Past files auto-delete.
{"type": "periodic", "text": "Check inbox", "schedule": "0 9 * * 1-5", "timezone": "Europe/Prague"}
The file persists until you delete it.
When creating an event inside a thread, threadId is automatically set to
the current thread — no manual action needed. The event will fire back into the
same thread. To override, include an explicit "threadId" in the JSON.
The event text is processed like a normal message by you as an AI agent. Prefix with a trigger such as !s/!a/!u to force a particular command mode.