AgentArmorHQ
Sign in
  • AgentArmor teamTeam4d agoNeeds helpSolved

    Roo-Code terminal commands hang or freeze on Windows/WSL — Roo bug or VS Code shell integration issue?

    On Roo-Code 3.8.1 (Windows/WSL, Ubuntu 24.04), a terminal command like lsb_release -d runs but Roo stays stuck on the spinner afterwards; 3.7.10 freezes completely, and 3.7.8 works. What is the status of these terminal integration hangs, and how can I tell whether the problem is in Roo-Code or in VS Code's shell integration?

    Originally asked on GitHub: https://github.com/RooCodeInc/Roo-Code/issues/1383

    5 answers

    • Best answerAgentArmor teamTeam4d ago

      This was a meta-issue for Shell/Terminal problems, not one bug with a single fix. It was closed in June 2025; the closing maintainer said there were no major ongoing issues left in this area producing numerous reports.

      What the thread establishes:

      • Maintainers point to upstream VS Code shell integration issues (microsoft/vscode#237208) and ask users to test with https://github.com/KJ7LNW/vsce-test-terminal-integration to find out whether a failure is a VS Code extension issue or a Roo-Code issue.
      • One reporter on Windows/WSL (Ubuntu 24.04) found a clear regression: Roo-Code 3.7.8 returned terminal output correctly, 3.7.10 froze completely with a no-entry mouse pointer, and 3.8.1 ran lsb_release -d but then stayed stuck on the spinner. The maintainer asked them to bisect versions and test PR #1365; no result from that test appears in this thread.
      • Workaround from the thread: if commands produce no output at all, close the terminal and let Roo open a fresh one for the next command. The contributor thought this might already be fixed by #1365 but said it needed more testing.
      • PR #1390 added middle-out truncation of long output. A contributor noted this is a feature, not a real fix: truncating output can hide an underlying terminal-handling bug.
      • The official troubleshooting guide is at http://docs.roocode.com/troubleshooting/shell-integration/.

      When reporting a terminal integration issue, the contributor asked reporters to click the chevron on the right of the API request and include the exact response Roo sent to the model, so the failure can be isolated.

      Did this work for you?
    • AgentArmor teamTeam4d ago

      What @sanderkooger tried on GitHub (Worked)

      On Windows/WSL (Ubuntu 24.04), ran a terminal command with Roo-Code 3.7.8 and received the output back as expected.

      Source: https://github.com/RooCodeInc/Roo-Code/issues/1383#issuecomment-2708427902 (opens external site)

      Did this work for you?
    • AgentArmor teamTeam4d ago

      What @sanderkooger tried on GitHub (Didn't work)

      Same environment with Roo-Code 3.7.10: the terminal command caused Roo to freeze completely with a no-entry mouse pointer.

      Source: https://github.com/RooCodeInc/Roo-Code/issues/1383#issuecomment-2708427902 (opens external site)

      Did this work for you?
    • AgentArmor teamTeam4d ago

      What @sanderkooger tried on GitHub (Didn't work)

      Same environment with Roo-Code 3.8.1: lsb_release -d executed, but Roo stayed on the spinning circle afterward and never returned the result.

      Source: https://github.com/RooCodeInc/Roo-Code/issues/1383#issuecomment-2708427902 (opens external site)

      Did this work for you?
    • AgentArmor teamTeam4d ago

      What @KJ7LNW tried on GitHub (Outcome unclear)

      Contributor suggested reproducing with https://github.com/KJ7LNW/vsce-test-terminal-integration to decide whether the issue is upstream VS Code shell integration or Roo-Code; no reporter confirmed the result of that test in this thread.

      Source: https://github.com/RooCodeInc/Roo-Code/issues/1383#issuecomment-2705160980 (opens external site)

      Did this work for you?

    Add your answer or comment