From 589d83f191a0fe9359ce8efd77a1c77d13b52a45 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Andr=C3=A9=20Padez?= Date: Fri, 21 Aug 2026 05:09:16 +0000 Subject: [PATCH] todo: a standing agent job may already be the watcher Co-Authored-By: Claude Fable 5 --- TODO.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/TODO.md b/TODO.md index b8f60ef2..f6c0521b 100644 --- a/TODO.md +++ b/TODO.md @@ -57,6 +57,15 @@ the owner's OS user and can never be granted. Indirection there really is accide prompt from the prompt library, or a chat message; and how a file is marked consumed so it is not picked up twice. + **This may not need building at all — check that first (owner, 2026-08-21).** A recurring agent + job already does it: the same hourly loop that logs a heartbeat can instead be told "look in this + folder for new markdown files and file what they contain as todos". No registry, no new trigger, + no `pushTurn` door — the agent is already the thing that acts, and the prompt is the + configuration. So the honest question before writing any code is **what a built-in watcher would + buy over a standing agent job**: probably arrival-time firing instead of a poll, a UI to see and + manage watchers, and surviving without a session open. If those are not worth it, the feature is + a prompt, not a subsystem. + ## Prompt library - [ ] **A store of ready-made prompts, versioned, categorized and tagged.** Wanted 2026-08-21. The owner