Continuous

Explicit multi-feature mode

Run $continuous in Codex or /continuous in Claude Code only when you want Blueprint to continue through the build plan without the normal per-step review pauses. Google Antigravity also uses /continuous. In GitHub Copilot or OpenCode, ask the agent to run the Continuous skill.

With no feature list, it resumes active feature work or selects the next unchecked build-plan item and continues in plan order.

Pending completion is reconciled first. continuous resume can finish an interrupted archive, commit, or merge without repeating completed work. It preserves the frozen build attempt and counts each completed feature once toward the run limit. Missing or conflicting recovery evidence stops before another feature begins.

One human-style lifecycle per feature

For each feature, Continuous Mode:

1. Writes or resumes the feature spec.
2. Creates the configured feature branch.
3. Implements and verifies small steps.
4. Applies the configured Continuous quality gates.
5. Archives the completed work.
6. Creates one clean local main commit and deletes the feature branch.
7. Selects the next unchecked feature.

Configured checkpoint commits can preserve passing implementation steps on the feature branch. Local main still receives one feature-level commit.

If the Continuous independent-review gate is selected, the run verifies the feature, prepares the approved code checkpoint and verified spec, and uses the configured execution method. Ignored specs use the same local snapshot contract as Audit. The default automatic path starts an isolated reviewer and waits for its receipt. If the runtime cannot prove fresh context, exact reviewer identity and model, and completion, Continuous preserves the request and stops with the manual fresh-session handoff. continuous resume continues only after a fresh reviewer writes a current passing receipt. When Audit is also selected, the independent pass satisfies it instead of running a duplicate builder review.

Limits and stopping conditions

continuous.maxFeatures can limit how many features finish in one run. continuous.maxRepairAttempts bounds repeated repair attempts, and continuous.finalIntegrationAudit can add a cross-feature audit at the end. See Project Configuration for every setting.

The run stops on missing decisions, unsafe Git state, failed verification, unresolved serious findings, merge conflicts, destructive work, or another boundary that needs human approval. A stopped run preserves its active branch, spec, checked steps, and commits so continuous resume can continue later.

Browser automation

When qualityGates.continuous.check is when-behavioral or always, Check runs the Browser tests command documented in AGENTS.md. Feature and Implement can add focused coverage for the current acceptance criteria, then Continuous Mode reuses that project-owned harness.

Continuous Mode never installs browser tooling mid-feature. Run Tests browser mode before Continuous Mode when the project needs a repeatable browser gate. If required UI evidence is unavailable, the run stops instead of claiming the behavior passed.

Hard boundaries

Continuous Mode never pushes, deploys, publishes, sends messages, changes remote services, performs destructive actions, accepts findings, or waives failed checks. Its explicit invocation authorizes only the local feature lifecycle.