A loop writes to its job panel and nobody reads a job panel, so a watcher that
fires overnight has done the work and told no one — which from the owner's side
looks the same as not firing.
Two messages, no more: what appeared and that it is being handled, then a short
report when the work ends. A progress commentary in chat is a notification per
step, which is how somebody turns notifications off.
The mechanism needs nothing new and no authentication. The child writes its report
to a file on the same machine as the same user; the loop inserts a nudge row for
its own transcript id over the local Postgres socket; the nudger wakes the
conversation within the minute and the commander reads the file and writes the
report itself. Facts in a file, judgement in the chat — which is what buys a
summary instead of a pasted log tail.
Notes the three things that bite: one nudge row per session so overwrite rather
than queue, the nudge message is a prompt to yourself and not what the owner
reads, and up to a minute late because the nudger polls on a minute.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
pastilhasandClaude Opus 5
39ce0953e4