From 61a98e767d7c45fb00b17f969c6fb42d2cbaca48 Mon Sep 17 00:00:00 2001 From: godosa Date: Wed, 7 Oct 2026 16:57:32 +0200 Subject: orch: one stuck task parks itself, lane keeps picking Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_01JEAjUkQRrCYX5MZhWxdtj2 --- docs/manual.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'docs/manual.md') diff --git a/docs/manual.md b/docs/manual.md index c9f7bd1..3d50ade 100644 --- a/docs/manual.md +++ b/docs/manual.md @@ -122,8 +122,8 @@ switches them to worktree mode (one branch per task, `wf finish` merges it). One After `/clear`, type `/wf-orchestrate` (`go` = start the proposed run without asking, `batch N` = prepare an unattended batch). The orchestrator holds no lane and never reads code. It spawns one fresh `wf-worker` per task (`wf orch pick` / `wf orch post`), one per lane in -parallel, on the task's model, and stops a lane on the first awaiting, handback or red -post-check. Use it when the backlog is runner-ready (section 3) and you want to steer. +parallel, on the task's model, and parks a task that ends awaiting, handback or red post-check +(blocked / `Sessions: owner`, alert) while its lane keeps going. Use it when the backlog is runner-ready (section 3) and you want to steer. ### Overnight: `/wf-pilot` `/wf-pilot [--batch 4] [--lanes a,b] [--for 8h]` in an idle session, which can be one you opened -- cgit