From 730ea0d713634edf1abcf16defe887b05a5accc0 Mon Sep 17 00:00:00 2001 From: NanoClaw User Date: Thu, 26 Mar 2026 15:05:53 +0000 Subject: [PATCH] fix: refine task scripts intro wording Use third-person voice and clearer terminology for the task scripts intro paragraph. Co-Authored-By: Claude Opus 4.6 (1M context) --- groups/global/CLAUDE.md | 2 +- groups/main/CLAUDE.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/groups/global/CLAUDE.md b/groups/global/CLAUDE.md index 935578a..11988bc 100644 --- a/groups/global/CLAUDE.md +++ b/groups/global/CLAUDE.md @@ -79,7 +79,7 @@ Standard Markdown works: `**bold**`, `*italic*`, `[links](url)`, `# headings`. ## Task Scripts -For any recurring task, use `schedule_task`. Tasks that wake the agent frequently — especially multiple times a day — consume API credits and can risk account restrictions. If a simple check can determine whether you need to act, add a `script` — it runs first, and you only wake up when the check passes. This keeps agent invocations to a minimum. If it's unclear whether the user wants a response every time or only when something requires attention, ask. +For any recurring task, use `schedule_task`. Frequent agent invocations — especially multiple times a day — consume API credits and can risk account restrictions. If a simple check can determine whether action is needed, add a `script` — it runs first, and the agent is only called when the check passes. This keeps invocations to a minimum. ### How it works diff --git a/groups/main/CLAUDE.md b/groups/main/CLAUDE.md index d3ea5f9..c901813 100644 --- a/groups/main/CLAUDE.md +++ b/groups/main/CLAUDE.md @@ -267,7 +267,7 @@ The task will run in that group's context with access to their files and memory. ## Task Scripts -For any recurring task, use `schedule_task`. Tasks that wake the agent frequently — especially multiple times a day — consume API credits and can risk account restrictions. If a simple check can determine whether you need to act, add a `script` — it runs first, and you only wake up when the check passes. This keeps agent invocations to a minimum. If it's unclear whether the user wants a response every time or only when something requires attention, ask. +For any recurring task, use `schedule_task`. Frequent agent invocations — especially multiple times a day — consume API credits and can risk account restrictions. If a simple check can determine whether action is needed, add a `script` — it runs first, and the agent is only called when the check passes. This keeps invocations to a minimum. ### How it works