Shell Integration Issue with Roo Extension

[Dayclone]

Which version of the app are you using?

3.7.12

Which API Provider are you using?

VS Code LM API

Which Model are you using?

Claude 3.5 Sonnet

What happened?

Issue Description

Roo is unable to detect shell integration despite it being activated in the terminal. The message "Shell Integration Unavailable" persists across multiple shell configurations.

Steps to reproduce

Reproduction Steps

1. Open VS Code Insiders
2. Terminal shows "Shell integration activated"
3. Attempt to execute commands through Roo
4. Roo displays: "Shell Integration Unavailable"

Relevant API REQUEST output

Additional context

Shell Integration Issue with Roo Extension

Environment

• VS Code: Version 1.98.0-insider (system setup)
• Roo Extension: Version 3.7.12
• OS: Windows 11
• PowerShell Version: 7

Issue Description

Roo is unable to detect shell integration despite it being activated in the terminal. The message "Shell Integration Unavailable" persists across multiple shell configurations.

Reproduction Steps

1. Open VS Code Insiders
2. Terminal shows "Shell integration activated"
3. Attempt to execute commands through Roo
4. Roo displays: "Shell Integration Unavailable"

Shells Tested

PowerShell 7

• Shell integration shows as activated
• Command line shows proper integration script loading:

Command line: C:\Program Files\PowerShell\7\pwsh.exe '-noexit' '-command' 'try { . "c:\Program Files\Microsoft VS Code Insiders\resources\app\out\vs\workbench\contrib\terminal\common\scripts\shellIntegration.ps1" } catch {}'

Git Bash

• Shell integration shows as activated
• Command line shows proper integration script loading:

Command line: C:\Program Files\Git\bin\bash.exe '--init-file' 'c:\Program Files\Microsoft VS Code Insiders\resources\app/out/vs/workbench/contrib/terminal/common/scripts/shellIntegration-bash.sh'

WSL Ubuntu

• Shell integration attempted but encountered similar issues

Configurations Attempted

1. Default VS Code terminal settings
2. Explicit shell integration settings in settings.json
3. Custom shell integration script loading through profile
4. Environment variables for shell detection
5. Multiple terminal profile configurations

Expected Behavior

• Roo should detect and use the shell integration that VS Code reports as activated

Actual Behavior

• Roo consistently shows "Shell Integration Unavailable"
• Terminal shows "Shell integration activated"
• Commands execute successfully in the terminal
• Output is visible in the terminal but not to Roo

Additional Notes

• Shell integration is confirmed working in VS Code itself (visible in terminal hover)
• Commands execute successfully and show output in terminal
• The issue persists across shell types and configurations
• Terminal initialization can be slow in some configurations

[KJ7LNW]

if for some reason it takes more than 4 seconds to activate the terminal then roo may believe shell integration is not available. if this is the case then we should turn up the time out; while this time out is possible, I think it is unlikely and am pointing it out just in case:

https://github.com/RooVetGit/Roo-Code/blob/f9cd2a96fd04903a2764e9fd7126996d398e3a52/src/integrations/terminal/Terminal.ts#L95-L104

Please test your problem with this plugin: https://github.com/KJ7LNW/vsce-test-terminal-integration

The plugin has a check box to enable and disable shell integration for testing and verifies that the proper text output is being received.

if VSCE shell integration does not work in the test plugin, then it will not work in Roo, in which case it could be an upstream VSCE problem.

the code in the test plugin is almost identical to the code in Roo, so it is very representative of actual shell integration use.

[tonyppe]

Same problem here:

• Win11
• fresh install of VSCODE from the marketplace
• install Roo Code, add API key
• Set terminal profile to Ubuntu WSL (so that when roo code executes code, the terminal that opens is WSL and not the windows in-built powershell
• reload vscode
• try and use roo code
• -- outcome = roo code starts a new terminal, there is some delay while WSL is launching but around 1 to 2 seconds (much less than 4 seconds), the command is executed but around the same time of being executed Roo Code flags a message that it cannot read the CLI output.

Are there other timers involved here or the same 4 seconds applies?

[KJ7LNW]

Are there other timers involved here or the same 4 seconds applies?

It means VSCE shell integration (not Roo) didn't receive \x1b]633;A, so then Roo times out waiting for VSCE after 4s.

More here: http://docs.roocode.com/troubleshooting/shell-integration/

[KJ7LNW]

Ohh! WSL doesn't have escapes, and its semi-remote, so windows can't pass it on.

Run code --locate-shell-integration-path bash from windows and copy the file to Ubuntu. Then source <file> in your .bashrc .

[KJ7LNW]

You're looking for shellIntegration-bash.sh

[tonyppe]

I just noticed every time roo code executes a command, it opens a new terminal window.. perhaps this is a tell-tale sign something is wrong on my side. I'll check the shell integrations! Thanks!

[KJ7LNW]

I just noticed every time roo code executes a command, it opens a new terminal window

That is correct because every time shell integration fails it removes it from the terminal registry class, so it cannot be reused.

[tonyppe]

Is there a guide how to fix this? I am unsure how to proceed as this does not work even when trying to use native powershell on Windows (avoiding using WSL and any issue with WSL).

I have removed vscode, deleted the directory in %appdata% and even installed older versions of roo but the same problem persists.

i didnt have any problems during install over the weekend on my personal PC and personal Laptop where both use remote ssh to access my IDE running on an Ubuntu VM on my network.

But now I am back in the office I want to demo this great software to a colleague and I hit this problem. I'm not really sure what to look for.
I understood your steps regarding "code --locate-shell-integration-path bash" and copying the .sh to Ubuntu WSL, Though this problem exists with powershell as the default terminal as well.

I think if I resolve this with powershell then it may be resolved for WSL, too.