Skip to content

Fix terminal input prompts to use askQuestions in autopilot mode#309583

Merged
meganrogge merged 2 commits intomainfrom
merogge/ask-auto
Apr 13, 2026
Merged

Fix terminal input prompts to use askQuestions in autopilot mode#309583
meganrogge merged 2 commits intomainfrom
merogge/ask-auto

Conversation

@meganrogge
Copy link
Copy Markdown
Collaborator

Fix #309524
When a terminal command
waits for input in autopilot mode, the agent was instructed to silently guess answers and send them directly; the user never saw what was answered or had a chance to review. Now the agent always goes through askQuestions, which in autopilot mode auto-responds instantly and renders a completed carousel summary in chat so the user can see exactly what values were provided on their behalf.

@meganrogge meganrogge self-assigned this Apr 13, 2026
Copilot AI review requested due to automatic review settings April 13, 2026 18:59
@meganrogge meganrogge added this to the 1.117.0 milestone Apr 13, 2026
@meganrogge meganrogge enabled auto-merge (squash) April 13, 2026 18:59
@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Apr 13, 2026

Screenshot Changes

Base: 1eb30178 Current: fba7a74a

Changed (1)

chat/aiCustomizations/aiCustomizationManagementEditor/McpBrowseMode/Light
Before After
before after

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the runInTerminal tool’s runtime steering text so that when a terminal command appears to be waiting for interactive input, the model is always instructed to go through vscode_askQuestions (instead of silently guessing and using send_to_terminal directly in auto-approve/autopilot-like modes). This aligns terminal-prompt handling with the askQuestions tool’s autopilot behavior (auto-response + rendered completed summary).

Changes:

  • Remove the auto-approve/autopilot-specific “do not ask the user; guess and send input” instruction path.
  • Always emit guidance that requires vscode_askQuestions, followed by one-at-a-time send_to_terminal + get_terminal_output between prompts (idle, input-needed, timeout, and background steering paths).
Show a summary per file
File Description
src/vs/workbench/contrib/terminalContrib/chatAgentTools/browser/tools/runInTerminalTool.ts Unifies terminal input-needed guidance to always route through vscode_askQuestions, removing the prior silent-guess path for auto-approve/autopilot-like sessions.

Copilot's findings

  • Files reviewed: 1/1 changed files
  • Comments generated: 0

mjbvz
mjbvz previously approved these changes Apr 13, 2026
# Conflicts:
#	src/vs/workbench/contrib/terminalContrib/chatAgentTools/browser/tools/runInTerminalTool.ts
@meganrogge meganrogge merged commit 8a73ca2 into main Apr 13, 2026
26 checks passed
@meganrogge meganrogge deleted the merogge/ask-auto branch April 13, 2026 20:08
meganrogge added a commit that referenced this pull request Apr 17, 2026
…esults

Fix eval regression by:
1. Restoring isAutoApproved branch at all 4 steering text injection sites
   so autopilot/benchmark mode uses direct send_to_terminal instead of
   forcing through askQuestions
2. Shortening all steering text from ~100 words to ~25 words per site
3. Shortening timeout wrapper text

Addresses bb77ece (#309050) and 8a73ca2 (#309583) regressions.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Section 5 unreachable: autopilot instruction block forbids ask_questions, and forced ask_questions still shows an interactive carousel

4 participants