t3-watch

Follow the t3-tots-rules skill (skills/t3-tots-rules/SKILL.md). Steps that use the box, ListMachines, routines, cards or SendToUser are Grok Bot only; other agents follow t3-tots-rules "Grok Bot only". A watch is a routine you create only when the user asks for one. It reports by default. In delegated mode (t3-tots-rules "Decisions") it may also answer, approve, nudge and resume.

Pick the check

• A T3 thread on a computer where t3listen runs with phone answers on: finished, failed and cancelled events already reach chat (t3-phone-answers). A watch is still useful for stalls, approvals and queue problems, which t3listen doesn't report.
• A T3 thread: t3ctl watch --thread '<id>[,<id2>]' --state watch-<name>.json --json. One call covers several threads and prints nothing when nothing changed. Give each watch routine its own state file, so two watches on one thread don't hide changes from each other.
• A log: tail -n 30 <log>. A process: pgrep -fl <name>.
• A PR: gh pr view <n> -R <owner/repo> --json state,statusCheckRollup,reviews,comments.
• T3 scheduled tasks: t3ctl tasks lists them. Create one only on an explicit ask, with --upsert ... --disabled first, then --enable once the user confirms.

Start a watch

1. Resolve the target and take one snapshot now with the same command and state file the routine will use. It prints a first event with the state, and the routine's first run then reports only real changes. Tell the user the state, including any queue-held or limit it shows.
2. Create a routine that runs every 10 minutes, or every 5 if they say "soon", with the prompt below filled in.
3. Reply in one line: what you're watching, how often, and the current state.

Don't set an end time unless the user gives one. A watch runs until the user stops it. When the work finishes, say so and offer to stop it.

Routine prompt

Watch <TARGET> on <COMPUTER> (machineId <ID>). Follow t3-tots-rules and t3-watch.
Mode: <report | delegated until <end condition>>.
Check: <the command from "Pick the check">
Rules:
- No changes in the output: send nothing and write nothing to memory or a journal.
- finished: tell the user "<TARGET> finished at <time>", 2 lines of result, offer files (t3-get-output) and offer to stop this watch. Report the finish only once, and skip it if t3listen already reported it in chat. A finish can also mean the thread is asking something or has a plan ready; say which.
- question, approval, limit, error, queue-held, queue-stuck, stale-request, quiet, stalled, unreadable: follow t3-watch "Handle an event".
- first, state, reply: send nothing, unless the user asked for progress updates.
- Computer unreachable, or T3 closed there (`T3_NOT_RUNNING`, `T3_NOT_REACHABLE`): tell the user once, then keep checking quietly until it is back.

Handle an event

In report mode, send the user one line per event: what it needs and the last reply in 200 characters or fewer. For limit, offer t3ctl resume-at-reset. Keep watching.

In delegated mode, act first and report after:

Keep a short log of what you decided and why, and send it to the user when they're back or when the watch ends.

Delegated mode

Start it when the user hands over control (t3-tots-rules "Decisions"). Before the first check:

1. Save the scope and the end condition to memory.
2. On a Mac, keep it awake for the run (t3-tots-rules "Computers").
3. Confirm in one line which threads, until when, and what you'll still ask about. Approvals are declined with a redirect and listed in the report, never accepted.