Note: I've created a minimal reproducible environment to help report issues with VSCode 1.93's new Terminal Shell Integration API. If the troubleshooting steps below don't resolve your issue, please follow the steps in that repository to report the problems you encounter.

• What is Shell Integration?
• How to Fix "Shell Integration Unavailable"
  • Step 1: Update VSCode or Cursor
  • Step 2: Configure VSCode to Use the Correct Shell
  • Step 3: Restart VSCode
• Additional Troubleshooting for Windows Users
  • Git Bash
  • PowerShell
    • Understanding PowerShell Execution Policies
    • Steps to Change the Execution Policy
• Still Having Trouble?
• Unusual Terminal Output
• Support

Shell integration is a new feature in VSCode 1.93 that allows extensions like Cline to run commands in your terminal and read their output. Command output allows Cline to react to the result of the command on his own, without you having to handhold by copy-pasting the output in yourself. It's also quite powerful when running development servers as it allows Cline to fix errors as the server logs them.

First, make sure you're using the latest version of VSCode or Cursor:

1. Open VSCode or Cursor
2. Press Cmd + Shift + P (Mac) or Ctrl + Shift + P (Windows/Linux)
3. Type "Check for Updates" (VSCode) or "Attempt Update" (Cursor) and select it
4. Restart VSCode/Cursor after the update

1. Open VSCode
2. Press Cmd + Shift + P (Mac) or Ctrl + Shift + P (Windows/Linux)
3. Type "Terminal: Select Default Profile" and choose it
4. Select one of the supported shells: zsh, bash, fish, or PowerShell.

After making these changes:

1. Quit VSCode completely
2. Reopen VSCode
3. Start a new Cline session (you can resume your previous task and try to run the command again, this time with Cline being able to see the output)

If you're using Windows and still experiencing issues with shell integration after trying the previous steps, it's recommended you use Git Bash.

Git Bash is a terminal emulator that provides a Unix-like command line experience on Windows. To use Git Bash, you need to:

1. Download and run the Git for Windows installer from https://git-scm.com/downloads/win
2. Quit and re-open VSCode
3. Press Ctrl + Shift + P to open the Command Palette
4. Type "Terminal: Select Default Profile" and choose it
5. Select "Git Bash"

If you'd still like to use PowerShell, make sure you're using an updated version (at least v7+).

• Check your current PowerShell version by running: $PSVersionTable.PSVersion
• If your version is below 7, update PowerShell.

You may also need to adjust your PowerShell execution policy. By default, PowerShell restricts script execution for security reasons.

PowerShell uses execution policies to determine which scripts can run on your system. Here are the most common policies:

• Restricted: No PowerShell scripts can run. This is the default setting.
• AllSigned: All scripts, including local ones, must be signed by a trusted publisher.
• RemoteSigned: Scripts created locally can run, but scripts downloaded from the internet must be signed.
• Unrestricted: No restrictions. Any script can run, though you will be warned before running internet-downloaded scripts.

For development work in VSCode, the RemoteSigned policy is generally recommended. It allows locally created scripts to run without restrictions while maintaining security for downloaded scripts. To learn more about PowerShell execution policies and understand the security implications of changing them, visit Microsoft's documentation: About Execution Policies.

1. Open PowerShell as an Administrator: Press Win + X and select "Windows PowerShell (Administrator)" or "Windows Terminal (Administrator)".

2. Check Current Execution Policy by running this command:

   Get-ExecutionPolicy

   • If the output is already RemoteSigned, Unrestricted, or Bypass, you likely don't need to change your execution policy. These policies should allow shell integration to work.
   • If the output is Restricted or AllSigned, you may need to change your policy to enable shell integration.

3. Change the Execution Policy by running the following command:

   Set-ExecutionPolicy RemoteSigned -Scope CurrentUser

   • This sets the policy to RemoteSigned for the current user only, which is safer than changing it system-wide.

4. Confirm the Change by typing Y and pressing Enter when prompted.

5. Verify the Policy Change by running Get-ExecutionPolicy again to confirm the new setting.

6. Restart VSCode and try the shell integration again.

If you're still experiencing issues after trying the basic troubleshooting steps, you can try manually installing shell integration.

For example, if you use zsh:

1. Run code ~/.zshrc in the terminal to open your zsh configuration file.
2. Add the following line to your ~/.zshrc:

[[ "$TERM_PROGRAM" == "vscode" ]] && . "$(code --locate-shell-integration-path zsh)"

3. Save the file.
4. Quit VSCode completely.
5. Reopen VSCode and start a new Cline session.

If you use PowerShell you would do:

1. Run code $Profile in the terminal to open your PowerShell profile.
2. Add the following line to the file:

if ($env:TERM_PROGRAM -eq "vscode") { . "$(code --locate-shell-integration-path pwsh)" }

If you're seeing unusual output with rectangles, lines, escape sequences, or control characters, it may be related to terminal customization tools. Common culprits include:

• Powerlevel10k: A zsh theme that adds visual elements to the prompt
• Oh My Zsh: A framework for managing zsh configurations
• Fish shell themes

To troubleshoot:

1. Temporarily disable these tools in your shell configuration file (e.g., ~/.zshrc for Zsh)
2. If the issue resolves, gradually re-enable features to identify the conflicting component

For example, if you're using Powerlevel10k with Zsh, you can disable it by commenting out the relevant line in your ~/.zshrc file:

# Comment out the Powerlevel10k source line
# source /path/to/powerlevel10k/powerlevel10k.zsh-theme

If disabling these customizations resolves the issue, you may need to find alternative configurations that are compatible with VSCode's shell integration feature.

If you’re using Windows and have OneDrive enabled on your PC, your desktop directory path might differ from a typical user. Terminal processes will look to launch from C:\Users<user>\Desktop, while Onedrive users will have a desktop path that looks like C:\Users<user>\Onedrive\Desktop. To solve this, we can create a symbolic link from the expected Desktop location to the actual OneDrive Desktop location.

1. Launch Command Prompt in administrator mode
2. Enter the command:

mklink /J "C:\Users\<username>\Desktop" "C:\Users\<username>\OneDrive\Desktop

3. Press Enter and close Command Prompt
4. Restart VSCode

If you've followed these steps and are still experiencing problems, please:

1. Check the Cline GitHub Issues to see if others have reported similar problems
2. If not, create a new issue with details about your operating system, VSCode/Cursor version, and the steps you've tried

For additional help, join our Discord.