https://github.com/pez/vscode-task-output-repro
Repro for vscode#304530: get_task_output subagent hang in multi-root workspace
https://github.com/pez/vscode-task-output-repro
Last synced: 10 days ago
JSON representation
Repro for vscode#304530: get_task_output subagent hang in multi-root workspace
- Host: GitHub
- URL: https://github.com/pez/vscode-task-output-repro
- Owner: PEZ
- Created: 2026-03-24T21:52:40.000Z (5 months ago)
- Default Branch: master
- Last Pushed: 2026-03-24T21:52:43.000Z (5 months ago)
- Last Synced: 2026-07-23T08:18:40.554Z (16 days ago)
- Size: 1000 Bytes
- Stars: 0
- Watchers: 0
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Repro: `get_task_output` subagent hang
Reproduction project for [vscode#304530](https://github.com/microsoft/vscode/issues/304530) — "When the agent uses the read task tool, things get stuck on 'Terminal is awaiting input'".
## Setup
1. Clone this repo
2. Create a sibling empty directory: `mkdir ../taskoutput2`
3. Open `taskoutput.code-workspace` in VS Code Insiders (multi-root workspace)
4. Run the **Dev** build task (`Cmd+Shift+B`) — starts 3 background tasks:
- **BB nREPL** — a fake long-running process (`tail -f /dev/null`)
- **Watch Unit Tests** — loops fake test output every ~7s
- **Watch E2E Tests** — loops fake test output every ~10s
## Reproducing the bug
1. Wait for all 3 tasks to be running in the terminal panel
2. In Copilot Chat, ask the agent to delegate checking task output to a subagent, e.g.:
> "Ask a subagent to check the test watcher status"
3. The subagent calls `get_task_output` and gets stuck
### Key observations
- **Direct** `get_task_output` calls from the main agent work fine
- **Subagent** calls to `get_task_output` get stuck consistently
- When stuck, the status bar shows "The task `Watch Unit Tests` is already running" — suggesting the tool call may be dispatched as a task **run** rather than a task output **read** from subagent context
- Multi-root workspace setup appears to be a factor
- Background tasks producing ongoing output (the loops) may contribute
## Project structure
```
taskoutput/
├── .vscode/
│ └── tasks.json # 3 background tasks + compound "Dev" task
├── taskoutput.code-workspace # Multi-root: this dir + empty ../taskoutput2
└── README.md
```
## Environment
- VS Code Insiders 1.113.x
- macOS (Apple Silicon)