todo: a standing agent job may already be the watcher

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-08-21 05:09:16 +00:00
parent 1f234c8282
commit 589d83f191
1 changed files with 9 additions and 0 deletions
@@ -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