The nudge

Part of team watch — the one fixed line the operator reads, and when the watch types it.

A report that is the operator's to act on is also what the nudge stands for. The lines around it:

LineMade when
watching the session "<session>" every <n>sat the start; , without nudges is added by --no-nudge
nudged the operator: Team watch: reports are waiting in .agents/team.logthe nudge was typed and sent
nudged the operator (its own unsent line was already in its box): <nudge>the box still held the line this same watch process had typed, its Enter never sent; that line is sent instead of typed again
nudge not typed (--no-nudge): <nudge>--no-nudge, with reports waiting
a nudge was typed and not sent: the operator's box does not hold itthe pane had not drawn the typed line, or held something else, when the bounded wait for it ended; nothing is sent, and the reports wait for the next pass
the operator could not be nudged for <n> minutes; <k> report(s) wait: <reports>the operator was busy for watch.nudge_wait; this one is a desktop notification too
herdr doesn't answer; the watch keeps tryingthe pass is skipped and the watch goes on
<account>: its check is unreadablethe check command failed, timed out, or printed something other than one to three lines for a subscription or one line for a spend account; its output is never logged
the check for <account> is unapproved; that account reads unknownthe check's file changed since the approval, or was never approved: it is not run
the session "<session>" is not this file's "<session>": its readings are not saved--session names a session other than the file's own; said once, on the first pass that sees it
team.yaml can't be read (<problem>); watching with the team as it wasthe file broke and no copy of it validated
closed <seat>; its end <until> holdsa temporary seat whose end is proved and whose pane is free was stopped
worktree <task> was not removedits removal failed; it is tried again on the next pass
the watch of "<session>" stoppedthe last line, on Ctrl-C or a stop signal

A question nudges the operator

A question is the operator's to act on, so the watch nudges the operator — one fixed line, which is not the report itself: the report is in the log, and the line says where.

Terminal
 team watch ; echo "exit $?"
2026-10-04T09:00:00.000Z watching the session "beacon" every 120s
2026-10-04T09:00:00.000Z claude-beacon asked a question: the operator's to act on
2026-10-04T09:00:00.000Z nudged the operator: Team watch: reports are waiting in .agents/team.log
2026-10-04T09:00:00.000Z the watch of "beacon" stopped
exit 0

--no-nudge keeps the reports

--no-nudge keeps the reports and skips the typing — for a watch whose operator is not to be interrupted at all:

Terminal
 team watch --no-nudge ; echo "exit $?"
2026-10-04T09:00:00.000Z watching the session "beacon" every 120s, without nudges
2026-10-04T09:00:00.000Z claude-beacon asked a question: the operator's to act on
2026-10-04T09:00:00.000Z nudge not typed (--no-nudge): Team watch: reports are waiting in .agents/team.log
2026-10-04T09:00:00.000Z the watch of "beacon" stopped
exit 0