From d51250bd23298c1c19f87eabe9021980dcb00924 Mon Sep 17 00:00:00 2001
From: zap <zap@local>
Date: Wed, 11 Mar 2026 20:19:33 +0000
Subject: [PATCH] docs(agents): default cron jobs to automation agent

---
 AGENTS.md | 4 ++++
 MEMORY.md | 1 +
 2 files changed, 5 insertions(+)

diff --git a/AGENTS.md b/AGENTS.md
index ff7f34c..e1520fe 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -228,6 +228,10 @@ You are free to edit `HEARTBEAT.md` with a short checklist or reminders. Keep it
 
 ### Heartbeat vs Cron: When to Use Each
 
+**Cron agent default:**
+- In direct sessions with Will, use the `automation` agent for cron jobs by default.
+- Only use a different agent if Will explicitly instructs otherwise in that session.
+
 **Use heartbeat when:**
 
 - Multiple checks can batch together (inbox + calendar + notifications in one turn)
diff --git a/MEMORY.md b/MEMORY.md
index 829fc82..3915409 100644
--- a/MEMORY.md
+++ b/MEMORY.md
@@ -32,6 +32,7 @@
 - Treat Telegram DMs and TUI/webchat as separate main-session contexts when `session.dmScope = "per-channel-peer"` is active.
 - Use local-first search by default: SearXNG first, then Brave-backed fallback when needed.
 - Brave free-plan search is rate-limited heavily; avoid parallel bursts.
+- In direct sessions with Will, cron jobs should use the `automation` agent by default unless Will explicitly says otherwise in that session.
 
 ## Infrastructure notes worth remembering
 - Full `~/.openclaw` backups upload to MinIO bucket `zap` and are scheduled via OS cron every 6 hours.