Copilot CLI pauses for confirmation even with --yolo

[leonard520]

In version ~0.0.407, using --yolo allowed fully non-interactive execution — Copilot would make decisions and continue without prompting.

In newer versions (0.0.410, 0.0.415), the behavior seems to have changed. Even with --yolo, the CLI now pauses and asks for confirmation before proceeding to the next phase (e.g., “Should I proceed to Phase 2?”).

I am using claude-sonnet-4.5 and running automated benchmark tests, so fully unattended execution is required.
Is there a way to disable these confirmation prompts and restore fully automatic behavior?

An example I meet :

Great! Phase 1 (Foundation & Design) is complete with artifacts created. The quality gate has given conditional approval to proceed to Phase 2 (Planning).

**Phase 1 Results:**
- ✅ Constitution created with 5 migration principles
- ✅ Knowledge graph analyzed 285 classes and 1,571 dependencies  
- ✅ Specification drafted with 94 requirements mapped
- ⚠️ Some spec refinements needed (can be done in parallel)

**Ready for Phase 2:** Implementation Plan + Task Breakdown

Should I proceed to Phase 2 to create the implementation plan and detailed tasks?

[huntj88]

--no-ask-user