Skip to main content

/continue-yolo

The autonomous sibling of /continue. It executes the exact same thirteen steps — there is one definition of the loop, and it lives in /continue. The only difference is pacing: /continue-yolo does not pause between steps. It runs straight through, stopping only at:

  1. Step 6 — the plan. Always pauses for human approval, in every mode. /continue-yolo cannot skip this; a wrong plan caught here is far cheaper than wrong code later.
  2. Step 2 — the pickup gates. A task with no repo pointer, an unreadable design reference (the assume-and-proceed trap), or contradictory readiness signals blocks here and waits for the human — autonomous pacing does not mean autonomous guessing. These are the most dangerous failure mode precisely because a run-through agent is tempted to infer the missing piece and proceed; it must not. See step 2 in /continue.
  3. Hard gates. Anything the autonomy model marks Hard-Floor or a matched policy marks human_approval_required, plus the git-hook / block-edit-on-master enforcement layers.

Everything else — the per-step Needs checks, the no-placeholder rule, state-sync checkpoints, /verify, PR open, review handling — is identical to /continue. Read /continue for the step definitions; this command does not duplicate them.

When to use which​

  • /continue — step-by-step. Pauses after each step for a quick confirm/adjust. The default; pick it when you want to supervise, when the task is risky or unfamiliar, or when you're teaching the loop to a new hire.
  • /continue-yolo — autonomous. Pick it for routine, well-understood work where you trust the run end-to-end and only want to be interrupted by the plan pause and real gates.

/continue-yolo is exactly equivalent to bare /continue with continueStepPause: false in ~/.bewith/config.json. The command is the explicit, per-invocation form; the config is the durable per-developer default. Either way, the Hard-Floor pauses still hold.

Cross-reference​

  • /continue — the canonical thirteen-step definition, the invocation modes (<n>, from <n>), and the per-step Needs table.
  • autonomy-model.md — the Hard-Floor + configurable gates that stop even an autonomous run.