Under the hood
Useful1 Signal2
Each scheduled task run now carries its own id, so a run can be traced back to its schedule.
What's wrong with this entry?
Anonymous. No account, no email.
What
Each scheduled-task firing now passes the task and a fresh per-run id through to the query it starts, so a run can be tied back to the schedule that triggered it.
Details
- The
/loopbranch no longer consults the separate loop-enabled check before rewriting the queue, and the "Claude resuming /loop wakeup" message variant is gone from this path; the scheduled-task variant remains.
Evidence
Running scheduled task (
Strings lifted out of the shipped bundle, so the claim above can be checked against them.