1 changed files with 1 additions and 1 deletions
@@ -28577,7 +28577,7 @@ Threshold values are shown for each flag. A value of **0.0** means always automa

 **`trusted`**: Strategize and Execute thresholds set to 0.0 (always automatic). Validation fixes, child plan spawning, and transient retries proceed automatically. Strategy revision and checkpoint restores remain manual (thresholds 1.0) to preserve human oversight over plan-level course corrections. The system pauses only before Apply (threshold 1.0) for human review of the final diffs. Use for: day-to-day feature development, routine refactoring, test generation.

-**`auto`**: All thresholds set to 0.0 except Apply (1.0). The system can revise its own strategy, restore from checkpoints, and handle all decisions automatically. Only Apply requires human approval. Use for: well-understood projects, batch operations, tasks with strong invariant coverage.
+**`auto`**: All thresholds set to 0.0 except `select_tool` (1.0), `access_network` (1.0), and `approve_plan` (0.0 — Apply is automatic). The system can revise its own strategy, restore from checkpoints, and handle all decisions automatically. Tool selection and network access require human approval. Use for: well-understood projects, batch operations, tasks with strong invariant coverage.

 **`ci`**: All thresholds set to 0.0 — complete end-to-end automation including Apply — but sandbox and checkpoints remain mandatory and unsafe tools are blocked. Designed for non-interactive environments where full automation is needed but safety nets must be preserved. Use for: CI/CD pipelines, automated testing workflows, scheduled batch jobs, any headless execution where rollback capability is essential.