VS Code agent cannot capture terminal output in WSL workspace
Maintainers usually reply within 8 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 52/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript, vscode
- Domain
- developer-experience, tooling
Research direction
Start by tracing the VS Code extension’s remote terminal execution path and compare it with local workspace handling, including the ide.runCommand path mentioned in #9679. Reproduce the issue with pwd in a WSL workspace, then verify that stdout, stderr, and exit status are returned without inserting commands into unfinished user input.
Written by the indexing model from the issue text.
Description
Environment
Windows with WSL2 (Ubuntu)
VS Code opened from a WSL directory using code .
Continue VS Code extension installed under both Local and WSL: Ubuntu
Continue version: 2.0.0
VS Code version: 1.140.0
Problem
When Continue’s agent runs a terminal command in the WSL workspace, the command text appears in the VS Code Ubuntu terminal. However, Continue receives neither the command’s output nor its exit status. The tool instead returns: "Command executed in remote terminal. Output capture is not yet available for remote environments"
This happens even with a harmless command such as pwd. The same command works when I run it myself in the Ubuntu terminal. In a local Windows workspace, Continue runs commands with output visible to the agent, so the failure appears specific to the remote-workspace execution path.
Steps to reproduce
On Windows, open a WSL2 Ubuntu workspace in VS Code by running code . from an Ubuntu directory.
Ask Continue in Agent mode to run pwd.
Observe that the command text is sent to an interactive Ubuntu terminal.
Observe that Continue receives the “Output capture is not yet available” message instead of the path or an exit status.
Expected behavior
Continue should execute the command in the WSL environment and return stdout, stderr, and exit status to the agent, as it does for local workspaces. It should not insert agent commands into a terminal containing unfinished user input.
Actual behavior and impact
The agent cannot determine whether a command ran or succeeded. This prevents it from reliably running tests, diagnosing build failures, or safely performing actions that require verification.
Related issues and PRs
#9731 — Terminal output not captured when Windows VS Code connects to WSL: Appears to describe this same VS Code extension behavior. It is closed, but the behavior remains reproducible.
#9679 — Use ide.runCommand when Windows host connects to WSL: Fixed a powershell.exe ENOENT error by routing commands through the VS Code terminal. That allows command text to reach WSL but does not provide output capture.
#9810 — Detect WSL and spawn appropriate shell: Changes the standalone CLI implementation, not the VS Code extension’s remote terminal output path. Its closure of #9731 does not appear to resolve this reproduction.
- Dominant language
- TypeScript
- Stars
- 36.5k
- Forks
- 5.6k
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from continuedev/continue
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
continuedev/continue#13486 ·
Maintainers usually reply within 8 days
-
Chat panel overflows horizontally when VS Code zoom level is increased (Cmd/Ctrl + +)Possibly taken @tang-ontheway claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
continuedev/continue#13483 ·
Maintainers usually reply within 8 days
-
Docs: show tool selection for a shared remote MCP endpointPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
continuedev/continue#13464 · 1 comment ·
Maintainers usually reply within 8 days
-
Inline code becomes unreadable in VS Code high-contrast themesPossibly taken @aminesayagh claimed this 21 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
continuedev/continue#13424 ·
Maintainers usually reply within 8 days
-
create_new_file writes a JSON file on one line when the model sends its contents as a JSON valuePossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
continuedev/continue#13363 ·
Maintainers usually reply within 8 days
All issues in continuedev/continue
Similar issues
-
area-templates triage:bot-seen triage:needs-human
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
microsoft/aspire#22356 · 1 comment ·
Maintainers usually reply within 1 day
-
Archiving an agent that is not loaded keeps its old updatedAtPossibly taken @luoph claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
content triage
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
contributor: external needs review severity: low
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
Enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
JSPrismarine/JSPrismarine#3214 ·
Maintainers usually reply within 1 day