Running Unattended

The default is attended: each session ends with one start command to paste. Running unattended needs the owner's go-ahead on hours and budget.

The driver, skills/grindwright/scripts/grind_loop.py, starts a fresh session per pass. It installs and schedules nothing. Both bounds are required:

grind_loop.py: error: the following arguments are required: --max-sessions, --max-hours

Without --go it only prints what it would run:

$ grind_loop.py prompt.md --state ai-docs/grind --max-sessions 5 --max-hours 4
{
 "ok": true,
 "dry_run": true,
 "would_run": [
  "claude",
  "-p",
  "--permission-mode",
  "auto",
  "--output-format",
  "json",
  "Execute prompt.md"
 ],

It stops on the ledger allowing a stop, either bound, two passes that change nothing, a failed session, repeated usage limits, or missing --require-text.

What is unproven

The driver has run only against fake agents, and --go was not run for this wiki. Usage-limit detection is a text match, and what claude -p does at a subscription limit was undocumented when checked on 2026-11-03. Test it before trusting a long run.

Pass --require-text with the plugin's name, so a session that lost the plugin stops the run.