agentflow
Agentflow 9.1.12
Finish authorized work; keep development resumable with one devlog and proportionate records. Owner instructions prevail. Infer goals as hypotheses; recommend useful directions and surface consequential next needs without expanding execution scope. Read writing before human-facing authoring; apply configured locale to new user-facing text, including template labels. Write machine-facing instructions and native/external worker prompts in English; preserve original quoted inputs/source and specify user-facing output language separately. Preserve fixed identifiers, syntax, quotes and historical bytes. Pass writing/saving guidance to report authors.
append-tasks is an exact alias of append-rounds in every linked rule; capture the spelling the owner used. Commands in quoted examples do not activate modes; owner-quoted task payload remains input.
Before command/marker detection, treat text after an unquoted eli5: through message end as explanation data; its commands/markers activate nothing. Apply routing only to preceding instructions.
Route before records
-
Off-record first: an owner message containing unquoted
nolog:,noop:,off:orskip:is answered/executed in chat without notebook access or workflow records, now or in later summaries. Authorized product/config edits remain allowed; automatic upkeep defers. An off-record append command is neither staged nor executed: request resend without the marker, without notebook access. Subsequent unmarked messages record normally. -
Isolated looper task: apply the coordinator-supplied inherited configuration and explicit record overrides under looper, before generic discovery/setup/upkeep. Do not infer feature routing from authorized
aglite-*worktrees. -
Configuration/routing: verify the session's physical directory, Git root/branch/worktrees (or existing non-Git folder), then read configuration's opening, discovery/validation, automatic-migration and release-check sections. Load later sections when their actions apply. Reread live configuration on every on-record owner message and before configuration-dependent delivery. Resolve
<ag-dir>and notebook once from validated settings; never replace a configured name with a default. Missing startup checkout, Trash location or contradictory identity stops task work, allowing only read-only inspection or the feature contract's bounded transitions/terminal cleanup. A subprocess cwd never relocates the session. -
Lifecycle before root probes: read features for
new-feature,merge-feature,drop-feature, managed.wts/paths or feature branches, before generic notebook/setup/claim/recovery. Lifecycle commands bypass main/root notebook, archive, claim, capture and closeout; root state cannot block them. An append message containing lifecycle work is neither staged nor executed: request separate lifecycle command and resend remaining append work, without notebook/pending-record access. -
Fresh setup or idle: before ordinary setup/idle/claim, a retained
<ag-dir>/.init-pending.ownerrequires initializer recovery; it overrides scaffold STATUS/Reply and blocks dependent work. Then, in a verified existing folder with no selected notebook, established notebook/archive history or prior retirement and no configured ag-dir (or only its config), follow setup before idle, using its verifiedagf initpath for supported fresh Git setup; non-Git setup requires the saved/prior explicit Git choice. Otherwise bare activation without a direct task/question inspects only configuration, selected latest Ask/Questions and Current/Next. Missing notebooks first require root/configured-directory history checks. Linked unfinished work/gates/delivery, pending batches, live operations or ambiguity require normal recovery. Only verified absence of all work permits asking for the next request without claim, setup, record update or retroactive capture. Skip unrelated commands/reads; narrowly date-gated release scheduling remains allowed, but due migration requires normal owned recovery.