Steps to Reproduce:
- Open Copilot Chat in VS Code and switch to Autopilot (Preview) mode
- Give Copilot a task that requires a decision (e.g. "Add a way to edit groups in my UI")
- Copilot analyzes the codebase and generates a clarification question via the
askQuestion tool (e.g. "Which approach do you want for editing groups? Option A or Option B?")
- The modal doesn't appear at all and Copilot immediately answers the question itself and continues execution
Actual Result:
Copilot picks an answer on its own (e.g. "Option A — Edit icon per card") and proceeds without waiting for user input. The question modal is shown but functionally useless since the agent doesn't pause.
Expected Result:
When Copilot calls askQuestion and displays a modal, execution should block until the user explicitly submits an answer. The agent should treat this as a hard pause point, not an optional hint.
Why this matters:
The askQuestion mechanism exists precisely for situations where the agent cannot or should not decide on its own. If the agent bypasses it, the feature is misleading, it creates the appearance of user control while ignoring the response entirely.
Steps to Reproduce:
askQuestiontool (e.g. "Which approach do you want for editing groups? Option A or Option B?")Actual Result:
Copilot picks an answer on its own (e.g. "Option A — Edit icon per card") and proceeds without waiting for user input. The question modal is shown but functionally useless since the agent doesn't pause.
Expected Result:
When Copilot calls
askQuestionand displays a modal, execution should block until the user explicitly submits an answer. The agent should treat this as a hard pause point, not an optional hint.Why this matters:
The
askQuestionmechanism exists precisely for situations where the agent cannot or should not decide on its own. If the agent bypasses it, the feature is misleading, it creates the appearance of user control while ignoring the response entirely.