Tools: getTaskOutput should not be under execute #281822
Description
Type: Bug
execute is framed as expected with "executing code".
🐛 getTaskOutput is in execute, while it is just a read-only operation on running tasks, which could be as well auto-started or manually started by the user.
VS Code version: Code - Insiders 1.107.0-insider (Universal) (6b29ec0, 2025-12-05T22:20:51.110Z)
OS version: Darwin arm64 25.1.0
Modes:
System Info
| Item | Value |
|---|---|
| CPUs | Apple M4 Pro (14 x 2400) |
| GPU Status | 2d_canvas: enabled direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled multiple_raster_threads: enabled_on opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok skia_graphite: enabled_on trees_in_viz: disabled_off video_decode: enabled video_encode: enabled webgl: enabled webgl2: enabled webgpu: enabled webnn: disabled_off |
| Load (avg) | 8, 8, 8 |
| Memory (System) | 24.00GB (0.14GB free) |
| Process Argv | --log trace --enable-proposed-api digitarald.agent-memory --enable-proposed-api digitarald.agent-handoff --crash-reporter-id 9b206efe-c338-4f34-baff-2aab1c48a82e |
| Screen Reader | no |
| VM | 0% |