roo code can't execute commands in zsh on mac

[MatthewMaierGHL]

App Version

3.11.15

API Provider

OpenRouter

Model Used

I don't see that specified anywhere

Actual vs. Expected Behavior

I'm on Mac with a fresh install of VScode and fresh activation of roo code. I was able to use boomerang tasks to create and edit project files, but it is not able to execute shell commands (in zsh). I expected it to just run the command when I click apply/run but instead it creates a "shell integration unavailable" error (see screenshot).
Shell Integration Unavailable
Shell integration initialization sequence '\x1b]633;A' was not received within 5s. Shell integration has been disabled for this terminal instance. Increase the timeout in the settings if necessary.
• Check terminal workarounds in the settings page
• Update VSCode (CMD/CTRL + Shift + P → "Update")
• Make sure you're using a supported shell: zsh, bash, fish, or PowerShell (CMD/CTRL + Shift + P → "Terminal: Select Default Profile")

Detailed Steps to Reproduce

1. install vscode on mac
2. add roo code extension, connect open router, setup .roomodes
3. ask roo code to execute a test shell command
4. click approve on the echo "Hello, world!" command
5. watch as it creates a "shell integration unavailable" error

Relevant API Request Output

[execute_command for 'echo "Hello, world!"'] Result:

Command executed in terminal 1 within working directory '/Users/mattmaier/Library/CloudStorage/GoogleDrive-matthew.maier@gohighlevel.com/My Drive/HLKB_chrome_extension'. Exit code: <undefined, notify user>
Output:
<no shell integration><VSCE exitDetails == undefined: terminal output and command execution status is unknown.>

<environment_details>
# VSCode Visible Files


# VSCode Open Tabs


# Current Time
4/14/2025, 6:34:37 AM (America/Los_Angeles, UTC-7:00)

# Current Context Size (Tokens)
11,575 (6%)

# Current Cost
$0.05

# Current Mode
<slug>code</slug>
<name>Code</name>
</environment_details>

Additional Context

No response

[dosubot]

Hello @MatthewMaierGHL! I'm here to help you solve bugs, answer your questions, and support you as a contributor. While you wait for a human maintainer, feel free to share more details, and we'll get this sorted out together!

I found a similar issue that was resolved by adjusting the terminal shell integration timeout. The solution involves configuring the timeout through the Advanced Settings UI, with values ranging from 1 to 60 seconds. This setting will persist across sessions using VSCode's globalState, which is useful if your terminal has longer startup times due to plugins and tools ^[1].

To resolve the "shell integration unavailable" error, follow these steps:

1. Update VSCode: Ensure you are using the latest version of VSCode (1.93+ is required for Roo Code's shell integration).

2. Select a Compatible Shell: Open the Command Palette (Cmd+Shift+P) and choose "Terminal: Select Default Profile". Make sure to select a compatible shell such as bash, zsh, PowerShell, or fish.

3. Adjust Terminal Shell Integration Timeout: Increase the timeout in the settings as mentioned in the error message. This can be done through the Advanced Settings UI.

4. Test with VSCode Terminal Integration Test Extension: Use the VSCode Terminal Integration Test Extension to determine if it's an upstream VSCode issue. If so, try updating to the latest VSCode Insiders build.

5. Ensure Shell Integration is Enabled: Verify that your environment is correctly configured to allow Roo Code to execute commands and process outputs.

6. Install Updated Roo Code Build: If you are experiencing terminal stalling issues, download and install the updated build from: https://www.linuxglobal.com/out/roo/roo-cline-3.11.12-fix-misc-terminal-issues.vsix. This update includes a workaround for ZSH shell integration issues ^[2].

7. Enable ZDOTDIR Option: Enable the ZDOTDIR option in the settings to help resolve terminal integration issues while keeping ZSH as the default shell.

By following these steps, you should be able to resolve the "shell integration unavailable" error and ensure smooth operation of Roo Code's shell integration features.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}

[plucked]

Enable ZDOTDIR Option was working for me, otherwise making bash default was also working, but I don't like this option.

[MatthewMaierGHL]

I got roo code to execute an echo command!
I had to manually create a .zshrc file in my user's home directory (using touch in the terminal). https://macpaw.com/how-to/zshrc-file-mac
Then I edited it with a text editor to add the line from roo code's docs https://docs.roocode.com/features/shell-integration
[[ "$TERM_PROGRAM" == "vscode" ]] && . "$(code --locate-shell-integration-path zsh)"
But when I opened a new terminal in vscode there was an error that code wasn't recognized.
so I used the command palette to get the command to add code to PATH https://medium.com/@zouyu1121/fixing-command-not-found-code-on-mac-a-guide-for-visual-studio-code-users-a12fce3f2b2f

After all that, roo code ran the echo command and saw the results.

[jaycetan]

FYI this bug also exists on my PC.

[MNUser69]

I found a fix. In vscode go to settings and search for terminal.integrated.inheritenv and turn that option off. I didn't have to do that when using Roo on windows or on Ubuntu but I had to do it on the Mac

[tankcdr]

MNUser69

terminal.integrated.inheritenv

this worked for me. I spent much of the day working on this after update RC to the latest version. Thanks.

[carvalab]

@MNUser69

terminal.integrated.inheritenv

This worked for me also, this is the solution. Thanks

[KJ7LNW]

terminal.integrated.inheritenv

neat! I thought something like that may have happened...

[KJ7LNW]

@jaycetan are you using zsh on your PC? More info, please.

[imkebe]

In my case the issue is that ZSH need some delay to initiate the config. I'm using a omz + powerlevel10k. This takes about 1-2s to load after spawning a terminal. While there is an option to add delay for terminal commands, there is no initial delay to be set to wait until new terminal will fully load.

You can spot it by the % . This shows the ZSH was initiated in a basic way. Quick fix it to manually zsh/source ~/.zshrc between the RooCode commands invocation.

[KJ7LNW]

In my case the issue is that ZSH need some delay to initiate the config.

I think this is what you want: https://docs.roocode.com/features/shell-integration#terminal-shell-integration-timeout

[imkebe]

In my case the issue is that ZSH need some delay to initiate the config.

I think this is what you want: https://docs.roocode.com/features/shell-integration#terminal-shell-integration-timeout

Thanks. I thought this is a command execution timeout at first. However despite i've set it to 30s sometimes the shell integration is not catching up because mentioned in this issue integration unavaible alert shows up from time to time. It helped however once every twenty times it shows for me.