From: Anderson A. Giacomolli <redacted>
Date: Mon, 9 Nov 2026 00:35:08 +0000 (-0300)
Subject: Start a turn when a schedule comes due
X-Git-Url: http://git.giacomolli.uk/onechat/commitdiff_plain/d008b46cbfc6348255e9b9a1fc009f0e4bd6aa2a?ds=sidebyside;hp=d008b46cbfc6348255e9b9a1fc009f0e4bd6aa2a

Start a turn when a schedule comes due

The daemon runs the schedules next to WhatsApp. At its time, a schedule
goes to the chat as a work message that starts with [Schedule ID] and
starts a turn of the root agent, which does the task or spawns a
subagent for long work. The message ends with the empty reply line, so a
task that finds nothing for the user gives no message.

The runner waits until the first due time, at most one minute at a time,
so it sees a suspend of the machine or a change of the clock within a
minute. A set or a remove wakes it. It logs all due schedules in due
order, flushes the log, ends each run in the file, and wakes the turn
loop once, as the WhatsApp batches do. A crash between the flush and the
file write makes a run repeat once. So a schedule that came due while
the daemon was stopped runs once at the next start, with the line that
the run is late.

Telegram does not send the work message, because the reply of the agent
carries its content. The terminal client shows it. The README describes
the schedules, the cron subset, the limit of 5 minutes, and the rules
for daylight saving time.

Issue: 60e4e4f
---