Bloks 2.5.19

Bloks 2.5.19

Restarts no longer replay old queued messages (#129). A message sent to a busy agent waits for the turn to finish; if Bloks restarts first, it is sent once afterwards, as before, but only if it was queued in the last 12 hours by this version. Anything older, or queued by an earlier version (whose age nobody can know, and which that version may already have answered), is marked Not sent in the chat with a Send again button instead of running on its own. It is taken out of the queue for good, so a later restart does not consider it either, and engines never see it as part of the conversation.

One-time routines for agents (#130). bloks routine --date 2026-10-08 --time 09:00 --prompt "…" files a routine that runs once, for "check whether the supplier answered on Thursday". A date that has passed or does not exist is refused on the spot. bloks routines now lists what is scheduled with when each runs next, one-time ones with their date, and bloks unroutine <id> drops one. Agents can now change and drop only their own routines.

Checks: a cheap command before waking an agent (#131). A watcher can now be a check: bloks watch --check "python3 scripts/supplier_replied.py" --every 30 --do "A supplier replied; read it and decide the next step". The command runs on schedule in the agent's folder without the model; exit 0 means there is something to do (what it printed goes to the agent), exit 1 means nothing. The first look is a baseline and the same finding twice in a row is not news, so a turn is spent only on something new. A check is stopped after 30 seconds, its output is capped, a few run at a time at most, and the existing watcher limits still apply. It runs with your saved secrets but never the agent's workspace credential. Because nobody approves each run, a check an agent writes waits for you to approve its command in Watchers before it ever runs, unless that agent already runs commands without asking, and only for as long as it does.