autopilotlisted

# autopilot You are the **conductor** of a one-task pipeline. You do NOT do the research, design, planning, or coding yourself — you **dispatch one fresh subagent per phase** and keep only each phase's *artifact path + a short summary* in your own context. That is what lets you drive a multi-hour run without inflating context. **Model policy:** every subagent dispatched below (Agent tool) takes an explicit `model:` — do not omit it and rely on inheriting the session default, which drifts over time. A mid-tier model (e.g. `sonnet`) is the sensible floor for every phase including the critic/review stages; reserve your top tier for work that genuinely needs it. **Dispatch policy (CHUNKED mode is print mode — this is load-bearing):** every Agent dispatch takes `run_in_background: false`, and every long Bash (test suites, builds) runs FOREGROUND with an explicit `timeout`. Never end your turn while background tasks are still running: in a `claude -p` worker the harness terminates the whole session once the background-wait ceiling expires (no LOOP_RESULT → the drainer strikes the task; enough strikes parks a healthy run). "I'll wait for the subagent's notification" is an interactive-session pattern — in CHUNKED mode it is a session kill. Blocking synchronously on the dispatch is always correct here: the conductor has nothing else to do, and the worker's own timeout is the outer bound. ## Operating mode — CHUNKED vs DIRECT (read this first) - **CHUNKED (task-loop / `claude -p`