You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: release-notes/v1_103.md
+38Lines changed: 38 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -151,6 +151,44 @@ Early terminal auto-approve settings were introduced last month. This release, t
151
151
152
152
- The auto approve reasoning is now logged to the Terminal Output channel. We plan to [surface this in the UI soon](https://github.com/microsoft/vscode/issues/256780).
153
153
154
+
### Input request detection for terminals and tasks
155
+
156
+
When you run a task or terminal command in agent mode, the agent now detects when the process requests user input. You will be prompted to respond in chat, with the default or first option surfaced as the primary action and other options available in a dropdown. This works for scripts and commands that require multiple confirmations, across all supported shells and both foreground and background terminals. If you type in the terminal while a prompt is present, the prompt will hide automatically. When options and descriptions are provided (such as `[Y] Yes [N] No`), these are surfaced in the confirmation prompt.
157
+
158
+
In the below example, a script containing multiple prompts for user input is run via the agent. Confirmation prompts appear and I accept the actions, allowing the terminal script to finish running and the agent to provide a summary of what transpired.
159
+
160
+

161
+
162
+
### Improved error detection for tasks with problem matchers
163
+
164
+
For tasks that use problem matchers, the agent now collects and surfaces errors based on the problem matcher results, rather than relying on the language model to evaluate output. Problems are presented in a dropdown within the chat progress message, allowing you to navigate directly to the problem location. This ensures that errors are reported only when relevant to the current task execution.
165
+
166
+
### Compound task support in agent mode
167
+
168
+
Agent mode now supports running compound tasks. When you run a compound task, the agent indicates progress and output for each dependent task, including any prompts for user input. This enables more complex workflows and better visibility into multi-step task execution.
169
+
170
+
In the example below, the VS Code - Build task is run. Output is assessed for each dependency task and a problem is surfaced to the user in the response and in the progress message dropdown.
171
+
172
+

173
+
174
+
### Accessibility: Focus chat confirmation action
175
+
176
+
We've added a command, **Focus Chat Confirmation**`(kb(workbench.action.chat.focusConfirmation))`, which will focus the confirmation dialog, if any, or announce to screen reader users that confirmation is not required.
177
+
178
+
### Track progress with task lists (Experimental)
179
+
180
+
**Setting**:`setting(chat.todoListTool.enabled)`
181
+
182
+
The great thing about agent mode is that you can give it a high-level task and have it implement it. As it plans the work and breaks it down into smaller tasks, it can be overwhelming to track the progress of all these individual tasks.
183
+
184
+
This milestone, we are introducing the task/todo list feature in chat to better help you see which tasks are completed and which ones are still pending. You can view the task list at the top of the Chat view, so you always have visibility into the progress being made. As the agent progresses through its work, it updates the task list.
185
+
186
+
Get started by giving the agent a high-level task and ask it to track its work in a todo list!
187
+
188
+
<video src="images/1_103/chat-todo-list.mp4" title="Video that shows the todo list in chat." autoplay loop controls muted></video>
189
+
190
+
This feature is still experimental and you can enable it with the `setting(chat.todoListTool.enabled)` setting.
191
+
154
192
### Improved model management experience
155
193
156
194
This iteration, we've revamped the chat provider API, which is responsible for language model access. Users are now able to select which models appear in their model picker, creating a more personalized and focused experience.
0 commit comments