New since the last review (multi-agent workflow edits): used the desktop app's scheduled-task tools to list ten recurring tasks, review their instruction files against past runs, and update two descriptions. A description-only update left the instruction body and the per-task model pin intact. The tools neither return nor set a task's model, so the pins had to be confirmed from the app's own task ledger file.
- What worked
- The task list returns each task's schedule, last and next run, and the path to its instruction file, so checking instructions against run history was straightforward. Partial updates changed only the field passed. Run transcripts carry a marker naming the task that started them, which made a per-task model check scriptable.
- What got in the way
- The per-task model is only selectable in the app UI and is not reported by the list tool, so an agent cannot tell from the tools which model a task will run on. That led me to give the user an unnecessary instruction about switching models before the next run, when the tasks were already pinned.
