Repository: RooVetGit/Roo-Code-Docs
Pull request #68: feat: add shell integration guide
Author: login: KJ7LNW
Labels: name: documentation
description: Improvements or additions to documentation
name: size:L
description: This PR changes 100-499 lines, ignoring generated files.
name: lgtm
description: This PR has been approved by a maintainer
Created: 2025-03-09T01:09:14Z | Merged: 2025-03-09T01:45:42Z

Add comprehensive shell integration documentation with:
- Detailed explanation of how shell integration works
- Installation and troubleshooting instructions
- Known issues and solutions
- Update FAQ to link to shell integration guide
- Add shell integration to sidebar navigation

please the merge this asap so I can reference it as a direct link from shell integration errors in of roo because currently that link points at an old cline wiki 
<!-- ELLIPSIS_HIDDEN -->

----

> [!IMPORTANT]
> Add comprehensive shell integration guide to documentation and update navigation and FAQ links.
> 
>   - **Documentation**:
>     - Adds `shell-integration.md` with detailed shell integration guide, including installation, troubleshooting, and known issues.
>     - Updates `faq.md` to link to the Shell Integration Guide for terminal command issues.
>   - **Navigation**:
>     - Adds `shell-integration` to `sidebars.ts` for sidebar navigation.
> 
> <sup>This description was created by </sup>[<img alt="Ellipsis" src="https://img.shields.io/badge/Ellipsis-blue?color=175173">](https://www.ellipsis.dev?ref=RooVetGit%2FRoo-Code-Docs&utm_source=github&utm_medium=referral)<sup> for 7d40cc63c3b857a45d2110521a3289c43871c7eb. It will automatically update as commits are pushed.</sup>

<!-- ELLIPSIS_HIDDEN -->


Diff:
diff --git a/docs/faq.md b/docs/faq.md
index 1eebe97b..6aa37ced 100644
--- a/docs/faq.md
+++ b/docs/faq.md
@@ -112,7 +112,7 @@ Yes, if you are using a provider with a model that support web browsing. Be mind
 
 ### Can Roo Code run commands in my terminal?
 
-Yes, Roo Code can execute commands in your VS Code terminal.  You will be prompted to approve each command before it's executed, unless you've enabled auto-approval for commands. Be extremely cautious about auto-approving commands.
+Yes, Roo Code can execute commands in your VS Code terminal.  You will be prompted to approve each command before it's executed, unless you've enabled auto-approval for commands. Be extremely cautious about auto-approving commands. If you're experiencing issues with terminal commands, see the [Shell Integration Guide](troubleshooting/shell-integration) for troubleshooting.
 
 ### How do I provide feedback to Roo Code?
 
diff --git a/docs/troubleshooting/shell-integration.md b/docs/troubleshooting/shell-integration.md
new file mode 100644
index 00000000..2490ee58
--- /dev/null
+++ b/docs/troubleshooting/shell-integration.md
@@ -0,0 +1,321 @@
+# Terminal Shell Integration
+
+## What is Shell Integration?
+
+Shell integration is a [new feature in VSCode 1.93](https://code.visualstudio.com/updates/v1_93#_terminal-shell-integration-api) that allows extensions like Roo Code to run commands in your terminal and read their output. Command output allows Roo Code to react to the result of the command on its 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 Roo Code to fix errors as the server logs them.
+
+## How Shell Integration Works
+
+Shell integration uses special terminal sequences (like ANSI escape codes) to mark different stages of command execution in your terminal. Here's how it works:
+
+1. **Activation**: When you open a terminal in VSCode, your shell sends an activation sequence (`\x1b]633;A\x07`) to initialize shell integration.
+
+2. **Command Lifecycle**: VSCode shell integration uses OSC (Operating System Command) sequence 633 to track each command's lifecycle:
+   - OSC 633 ; A - Mark prompt start
+   - OSC 633 ; B - Mark command start
+   - OSC 633 ; C - Mark command executed (pre-output)
+   - OSC 633 ; D [; `<exitcode>`] - Mark command finished with optional exit code
+   - OSC 633 ; E ; `<commandline>` [; `<nonce>`] - Explicitly set command line with optional nonce
+   - OSC 633 ; P ; `<Property>=<Value>` - Set properties like current working directory
+
+3. **Shell Integration Hooks**: Each shell uses specific hooks for different stages of command execution:
+
+   - Bash:
+     * Initial activation: `PROMPT_COMMAND` (sets up initial environment)
+     * Command start: `trap DEBUG` (triggers before command execution)
+     * Command stop: `PROMPT_COMMAND` (triggers after command completion)
+
+   - Zsh:
+     * Initial activation: `precmd` (sets up initial environment)
+     * Command start: `preexec` (triggers before command execution)
+     * Command stop: `precmd` (triggers after command completion)
+
+   - PowerShell:
+     * Initial activation: `prompt` function (sets up initial environment)
+     * Command input: `PSConsoleHostReadLine` (captures command input)
+     * Command start/stop: `prompt` function (handles both command start and completion)
+
+   - Fish:
+     * Initial activation: `fish_prompt` (sets up initial environment)
+     * Command start: `fish_preexec` (triggers before command execution)
+     * Command stop: `fish_prompt` (triggers after command completion)
+
+> **Note:** This hook implementation information was discovered through AI inspection of the VSCode source tree. If you find any inaccuracies, please submit a pull request with corrections.
+
+These hooks emit OSC (Operating System Command) sequences that VSCode recognizes to track:
+   - Prompt start/end positions
+   - Command start/execution/finish events
+   - Current working directory changes
+   - Command line content and execution status
+
+4. **Output Capture**: When a command runs, VSCode captures:
+   - Command text and working directory
+   - Start and end times
+   - Exit codes
+   - Output streams (stdout/stderr)
+
+This allows VSCode and extensions like Roo Code to:
+- Know exactly when commands start and finish
+- Capture command output reliably
+- Track command success/failure
+- Update the terminal UI with command status
+- React to command results automatically
+- Track the current working directory
+
+## How to Fix "Shell Integration Unavailable"
+
+### Step 1: Update VSCode or Cursor
+
+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
+
+### Step 2: Configure VSCode to Use the Correct Shell
+
+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.
+
+### Step 3: Restart VSCode
+
+After making these changes:
+
+1. Quit VSCode completely
+2. Reopen VSCode
+3. Start a new Roo Code session (you can resume your previous task and try to run the command again, this time with Roo Code being able to see the output)
+
+## Additional Troubleshooting for Windows Users
+
+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
+
+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](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"
+
+### PowerShell
+
+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](https://learn.microsoft.com/en-us/powershell/scripting/whats-new/migrating-from-windows-powershell-51-to-powershell-7?view=powershell-7.4#installing-powershell-7).
+
+#### Understanding PowerShell Execution Policies
+
+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](https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_execution_policies).
+
+#### Steps to Change the Execution Policy
+
+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:
+     ```powershell
+     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:
+     ```powershell
+     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.
+
+## Manual Shell Integration Installation
+
+If you're still experiencing issues after trying the basic troubleshooting steps, you can try manually installing shell integration:
+
+### Installation Instructions
+
+For Bash users:
+1. Run `code ~/.bashrc` in the terminal to open your bash configuration file.
+2. Add the following line to your `~/.bashrc`:
+```bash
+[[ "$TERM_PROGRAM" == "vscode" ]] && . "$(code --locate-shell-integration-path bash)"
+```
+
+For Zsh users:
+1. Run `code ~/.zshrc` in the terminal to open your zsh configuration file.
+2. Add the following line to your `~/.zshrc`:
+```bash
+[[ "$TERM_PROGRAM" == "vscode" ]] && . "$(code --locate-shell-integration-path zsh)"
+```
+
+For PowerShell users:
+1. Run `code $Profile` in the terminal to open your PowerShell profile.
+2. Add the following line to the file:
+```powershell
+if ($env:TERM_PROGRAM -eq "vscode") { . "$(code --locate-shell-integration-path pwsh)" }
+```
+
+For Fish users:
+1. Run `code ~/.config/fish/config.fish` in the terminal to open your fish configuration file.
+2. Add the following line to your `~/.config/fish/config.fish`:
+```fish
+string match -q "$TERM_PROGRAM" "vscode"; and . (code --locate-shell-integration-path fish)
+```
+
+### About the Shell Integration Path Command
+
+The `code --locate-shell-integration-path` command returns the path to shell-specific integration scripts. It supports four shell types:
+- bash - returns path to `shellIntegration-bash.sh`
+- zsh - returns path to `shellIntegration-rc.zsh`
+- pwsh - returns path to `shellIntegration.ps1`
+- fish - returns path to `shellIntegration.fish`
+
+Any other value will throw an error: "Error using `--locate-shell-integration-path`: Invalid shell type".
+
+## Unusual Terminal Output
+
+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. If using Powerlevel10k, you must set `typeset -g POWERLEVEL9K_TERM_SHELL_INTEGRATION=true` in your `~/.zshrc` before sourcing the theme. This enables proper integration with VSCode's shell integration, which differs from the integration provided by VSCE.
+- Oh My Zsh: A framework for managing zsh configurations
+- Fish shell themes
+
+To troubleshoot:
+
+1. For Powerlevel10k users:
+   ```bash
+   # Add this line before sourcing powerlevel10k in ~/.zshrc
+   typeset -g POWERLEVEL9K_TERM_SHELL_INTEGRATION=true
+   ```
+
+2. If issues persist, temporarily disable these tools in your shell configuration file (e.g., `~/.zshrc` for Zsh)
+3. If the issue resolves, gradually re-enable features to identify the conflicting component
+
+## Advanced Troubleshooting
+
+### Shell Integration Not Available
+
+Shell integration activation sequence (`\x1b]633;A\x07`) was not received. Shell integration features are disabled. Verify you are using a supported shell (Bash, Zsh, PowerShell, Fish) and shell integration is enabled in settings.
+
+### Command Stream Not Available
+
+Command stream failed: missing start sequence (`\x1b]633;C\x07`) or command already ended (`\x1b]633;D\x07`). Command output cannot be captured. Check if the command started correctly or has completed execution.
+
+### Verifying Shell Integration Status
+
+Run these commands to verify shell integration sequences are installed:
+
+#### Bash
+```bash
+# View all shell integration sequences
+set | grep -i '[16]33;'
+
+# Should show VSCode shell integration functions like:
+# printf '\e]633;E;%s;%s\a' - Command line set
+# printf '\e]633;C\a' - Command executed
+# printf '\e]633;D\a' - Command finished
+# printf '\e]633;B\a' - Command start
+# printf '\e]633;A\a' - Shell integration activated
+# printf '\e]633;P;Prompt=%s\a' - Prompt marker
+
+# Check for PROMPT_COMMAND and DEBUG trap
+echo "$PROMPT_COMMAND" | grep vsc
+trap -p DEBUG | grep vsc
+```
+
+#### Zsh
+```zsh
+# List all VSCode shell integration functions
+functions | grep -i vsc  # Should show __vsc_precmd, __vsc_preexec, etc.
+
+# Verify shell integration hooks are installed
+typeset -p precmd_functions preexec_functions  # Should include __vsc_precmd and __vsc_preexec
+
+# Check Powerlevel10k integration (if installed)
+(( ${+functions[p10k]} )) && typeset -p POWERLEVEL9K_TERM_SHELL_INTEGRATION  # Should show "true"
+```
+
+#### PowerShell
+```powershell
+# View shell integration functions
+Get-Command -Name "*VSC*" -CommandType Function
+
+# Check prompt function
+Get-Content Function:\Prompt | Select-String "VSCode"
+```
+
+#### Fish
+```fish
+# Check for shell integration functions
+functions | grep -i vsc
+
+# Verify fish_prompt and fish_preexec hooks
+functions fish_prompt | grep -i vsc
+functions fish_preexec | grep -i vsc
+```
+
+Visual indicators of active shell integration:
+1. Shell integration indicator in terminal title bar
+2. Command detection highlighting
+3. Working directory updates in terminal title
+4. Command duration reporting
+5. Exit code reporting for failed commands
+
+## Troubleshooting Terminal Execution Failures
+
+If commands that previously worked suddenly stop working:
+1. Close the current terminal
+2. Let Roo Code open a new terminal for you
+3. Try your command again
+
+This often resolves temporary shell integration issues. However, if you experience persistent terminal execution failures and can reliably reproduce the problem, please [open a ticket](https://github.com/RooVetGit/Roo-Code/issues/new) with:
+- A step-by-step reproduction of the problem
+- Your operating system and VSCode/Cursor version
+- The shell you're using (Bash, Zsh, PowerShell, Fish)
+- Any relevant error messages or terminal output
+
+This will help us investigate and fix the underlying issue.
+
+## Known Issues
+
+### Incomplete Terminal Output
+
+There is an ongoing issue in VSCode where terminal command output may not be completely captured by extensions like Roo Code. This can result in:
+- Missing portions of command output
+- Incomplete error messages
+- Delayed or missing command completion signals
+
+If you experience this issue, try:
+1. Closing and reopening the terminal
+2. Running the command again
+3. If the problem persists, you may need to manually copy-paste relevant output to Roo Code
+
+## Troubleshooting Resources
+
+- [VSCode Terminal Output Issue #237208](https://github.com/microsoft/vscode/issues/237208): Tracking the incomplete terminal output capture issue (ongoing as of March 8, 2025)
+- [VSCode Terminal Integration Test Repository](https://github.com/KJ7LNW/vsce-test-terminal-integration): A tool for validating shell integration functionality in your environment
+- [Shell Integration Improvements PR](https://github.com/cline/cline/pull/1089): Enhanced shell integration behavior (merged in Roo Code as of March 8, 2025, pending merge in Cline)
+- [Roo Code Shell Integration Architecture PR](https://github.com/RooVetGit/Roo-Code/pull/1365): Detailed discussion and proposed architectural changes for more reliable shell integration (pending as of March 8, 2025)
+
+## Support
+
+If you've followed these steps and are still experiencing problems, please:
+
+1. Check the [Roo Code GitHub Issues](https://github.com/RooVetGit/Roo-Code/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](https://discord.com/channels/1332146336664915968/1332212137568899162).
\ No newline at end of file
diff --git a/sidebars.ts b/sidebars.ts
index c2aef510..4fb092f4 100644
--- a/sidebars.ts
+++ b/sidebars.ts
@@ -65,6 +65,13 @@ const sidebars: SidebarsConfig = {
       ]
     },
     'faq',
+    {
+      type: 'category',
+      label: 'Troubleshooting',
+      items: [
+        'troubleshooting/shell-integration',
+      ],
+    },
     'tutorial-videos',
     'community',
   ],


Reviews:
user: login: ellipsis-dev[bot]
body: :x: Changes requested. Reviewed everything up to 7d40cc63c3b857a45d2110521a3289c43871c7eb in <ellipsistime>1 minute and 45 seconds</ellipsistime>

<details>
<summary>More details</summary>

 - Looked at `358` lines of code in `3` files
 - Skipped `0` files when reviewing.
 - Skipped posting `6` drafted comments based on config settings.


<details>
<summary>1. <code>docs/faq.md:113</code></summary>

- **Draft comment:** 
Ensure that the relative link `[Shell Integration Guide](shell-integration)` correctly resolves in your Docusaurus setup. If file extensions or directory adjustments are required, update accordingly.
- **Reason this comment was not posted:** 
Comment did not seem useful. Confidence is useful = `0%` <= threshold `50%`
This comment is asking the PR author to ensure that a link resolves correctly, which is similar to asking them to double-check something. This violates the rule against asking the author to confirm or ensure things. Therefore, this comment should not be approved.

</details>

<details>
<summary>2. <code>docs/shell-integration.md:326</code></summary>

- **Draft comment:** 
Add a newline at the end of the file to conform with common formatting practices and Prettier/ESLint rules.
- **Reason this comment was not posted:** 
Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 0% vs. threshold = 50%
While having a trailing newline is a common convention and often enforced by linters, this kind of formatting issue should be handled automatically by configured tools rather than manual review comments. The rules state that we should assume ESLint and Prettier are set up for enforcing code style rules. These tools would automatically fix trailing newline issues if configured properly.
The comment is technically correct - having a trailing newline is good practice. And this is a new file being added, so the issue is related to a change.
However, per the rules, we should assume proper tooling is in place to handle code style automatically. Making manual comments about formatting issues that should be handled by tools adds noise to the review.
The comment should be removed since formatting issues like trailing newlines should be handled by automated tools rather than manual review comments.

</details>

<details>
<summary>3. <code>sidebars.ts:67</code></summary>

- **Draft comment:** 
The addition of 'shell-integration' to the sidebar is correct; ensure that its identifier matches the intended document ID for consistency.
- **Reason this comment was not posted:** 
Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 10% vs. threshold = 50%
This comment violates several rules. First, it asks to "ensure" something, which falls under the "do not ask to verify" rule. Second, there's no evidence that 'shell-integration' is incorrect - it follows the same naming pattern as other entries. Third, without seeing the actual documentation files, we can't know if this ID is wrong. The comment is speculative.
Maybe there's a naming convention I'm not aware of that requires the '-id' suffix. Maybe the actual documentation file does use a different ID.
Even if there were such conventions, the comment should point to specific evidence rather than asking for verification. And the pattern shown in the file suggests the simple kebab-case IDs are correct.
Delete this comment as it asks for unnecessary verification and makes a speculative suggestion without evidence.

</details>

<details>
<summary>4. <code>docs/faq.md:113</code></summary>

- **Draft comment:** 
Consider using an absolute or a clearly defined relative link (e.g., '/docs/shell-integration') for the Shell Integration Guide to ensure proper navigation in all environments.
- **Reason this comment was not posted:** 
Comment looked like it was already resolved.

</details>

<details>
<summary>5. <code>sidebars.ts:68</code></summary>

- **Draft comment:** 
Ensure that the 'shell-integration' entry is correctly positioned and that its corresponding document exists at the expected route.
- **Reason this comment was not posted:** 
Confidence changes required: `50%` <= threshold `50%`
None

</details>

<details>
<summary>6. <code>docs/faq.md:109</code></summary>

- **Draft comment:** 
There's a typographical error: 'model that support web browsing' should be corrected to 'model that supports web browsing' for proper subject-verb agreement.
- **Reason this comment was not posted:** 
Comment was not on a location in the diff, so it can't be submitted as a review comment.

</details>


Workflow ID: <workflowid>`wflow_5fB28V5ORnWX3dWZ`</workflowid>

</details>


----
**Want Ellipsis to fix these issues?** Tag `@ellipsis-dev` in a comment. You can customize Ellipsis with :+1: / :-1: [feedback](https://docs.ellipsis.dev/review), review rules, user-specific overrides, `quiet` mode, and [more](https://docs.ellipsis.dev/config).

state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-09T01:11:04Z
user: login: cte
body: This is amazing!
state: APPROVED
author_association: COLLABORATOR
submitted_at: 2025-03-09T01:12:36Z
user: login: mrubens
body: Content is great, but I don’t think this should be a top-level page. Can you put it under a Troubleshooting category (directory and in the sidebar) and update the links? Thank you!
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-03-09T01:12:58Z
user: login: mrubens
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-03-09T01:35:29Z
user: login: KJ7LNW
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-09T01:43:39Z
user: login: KJ7LNW
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-09T01:44:30Z
user: login: mrubens
state: APPROVED
author_association: COLLABORATOR
submitted_at: 2025-03-09T01:45:33Z

Review comments:
diff_hunk: @@ -0,0 +1,326 @@
+# Terminal Shell Integration Guide
+
+## What is Shell Integration?
+
+Shell integration is a [new feature in VSCode 1.93](https://code.visualstudio.com/updates/v1_93#_terminal-shell-integration-api) that allows extensions like Roo Code to run commands in your terminal and read their output. Command output allows Roo Code to react to the result of the command on its 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 Roo Code to fix errors as the server logs them.
+
+## How Shell Integration Works
+
+Shell integration uses special terminal sequences (like ANSI escape codes) to mark different stages of command execution in your terminal. Here's how it works:
+
+1. **Activation**: When you open a terminal in VSCode, your shell sends an activation sequence (`\x1b]633;A\x07`) to initialize shell integration.
+
+2. **Command Lifecycle**: VSCode shell integration uses OSC (Operating System Command) sequence 633 to track each command's lifecycle:
+   - OSC 633 ; A - Mark prompt start
+   - OSC 633 ; B - Mark command start
+   - OSC 633 ; C - Mark command executed (pre-output)
+   - OSC 633 ; D [; `<exitcode>`] - Mark command finished with optional exit code
+   - OSC 633 ; E ; `<commandline>` [; `<nonce>`] - Explicitly set command line with optional nonce
+   - OSC 633 ; P ; `<Property>=<Value>` - Set properties like current working directory
+
+3. **Shell Integration Hooks**: Each shell uses specific hooks for different stages of command execution:
+
+   - Bash:
+     * Initial activation: `PROMPT_COMMAND` (sets up initial environment)
+     * Command start: `trap DEBUG` (triggers before command execution)
+     * Command stop: `PROMPT_COMMAND` (triggers after command completion)
+
+   - Zsh:
+     * Initial activation: `precmd` (sets up initial environment)
+     * Command start: `preexec` (triggers before command execution)
+     * Command stop: `precmd` (triggers after command completion)
+
+   - PowerShell:
+     * Initial activation: `prompt` function (sets up initial environment)
+     * Command input: `PSConsoleHostReadLine` (captures command input)
+     * Command start/stop: `prompt` function (handles both command start and completion)
+
+   - Fish:
+     * Initial activation: `fish_prompt` (sets up initial environment)
+     * Command start: `fish_preexec` (triggers before command execution)
+     * Command stop: `fish_prompt` (triggers after command completion)
+
+> **Note:** This hook implementation information was discovered through AI inspection of the VSCode source tree. If you find any inaccuracies, please submit a pull request with corrections.
+
+These hooks emit OSC (Operating System Command) sequences that VSCode recognizes to track:
+   - Prompt start/end positions
+   - Command start/execution/finish events
+   - Current working directory changes
+   - Command line content and execution status
+
+4. **Output Capture**: When a command runs, VSCode captures:
+   - Command text and working directory
+   - Start and end times
+   - Exit codes
+   - Output streams (stdout/stderr)
+
+This allows VSCode and extensions like Roo Code to:
+- Know exactly when commands start and finish
+- Capture command output reliably
+- Track command success/failure
+- Update the terminal UI with command status
+- React to command results automatically
+- Track the current working directory
+
+## How to Fix "Shell Integration Unavailable"
+
+### Step 1: Update VSCode or Cursor
+
+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
+
+### Step 2: Configure VSCode to Use the Correct Shell
+
+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.
+
+### Step 3: Restart VSCode
+
+After making these changes:
+
+1. Quit VSCode completely
+2. Reopen VSCode
+3. Start a new Roo Code session (you can resume your previous task and try to run the command again, this time with Roo Code being able to see the output)
+
+## Additional Troubleshooting for Windows Users
+
+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
+
+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](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"
+
+### PowerShell
+
+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](https://learn.microsoft.com/en-us/powershell/scripting/whats-new/migrating-from-windows-powershell-51-to-powershell-7?view=powershell-7.4#installing-powershell-7).
+
+#### Understanding PowerShell Execution Policies
+
+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](https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_execution_policies).
+
+#### Steps to Change the Execution Policy
+
+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:
+     ```powershell
+     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:
+     ```powershell
+     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.
+
+## Manual Shell Integration Installation
+
+If you're still experiencing issues after trying the basic troubleshooting steps, you can try manually installing shell integration:
+
+### Installation Instructions
+
+For Bash users:
+1. Run `code ~/.bashrc` in the terminal to open your bash configuration file.
+2. Add the following line to your `~/.bashrc`:
+```bash
+[[ "$TERM_PROGRAM" == "vscode" ]] && . "$(code --locate-shell-integration-path bash)"
+```
+
+For Zsh users:
+1. Run `code ~/.zshrc` in the terminal to open your zsh configuration file.
+2. Add the following line to your `~/.zshrc`:
+```bash
+[[ "$TERM_PROGRAM" == "vscode" ]] && . "$(code --locate-shell-integration-path zsh)"
+```
+
+For PowerShell users:
+1. Run `code $Profile` in the terminal to open your PowerShell profile.
+2. Add the following line to the file:
+```powershell
+if ($env:TERM_PROGRAM -eq "vscode") { . "$(code --locate-shell-integration-path pwsh)" }
+```
+
+For Fish users:
+1. Run `code ~/.config/fish/config.fish` in the terminal to open your fish configuration file.
+2. Add the following line to your `~/.config/fish/config.fish`:
+```fish
+string match -q "$TERM_PROGRAM" "vscode"; and . (code --locate-shell-integration-path fish)
+```
+
+### About the Shell Integration Path Command
+
+The `code --locate-shell-integration-path` command returns the path to shell-specific integration scripts. It supports four shell types:
+- bash - returns path to `shellIntegration-bash.sh`
+- zsh - returns path to `shellIntegration-rc.zsh`
+- pwsh - returns path to `shellIntegration.ps1`
+- fish - returns path to `shellIntegration.fish`
+
+Any other value will throw an error: "Error using `--locate-shell-integration-path`: Invalid shell type".
+
+## Unusual Terminal Output
+
+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. If using Powerlevel10k, you must set `typeset -g POWERLEVEL9K_TERM_SHELL_INTEGRATION=true` in your `~/.zshrc` before sourcing the theme. This enables proper integration with VSCode's shell integration, which differs from the integration provided by VSCE.
+- Oh My Zsh: A framework for managing zsh configurations
+- Fish shell themes
+
+To troubleshoot:
+
+1. For Powerlevel10k users:
+   ```bash
+   # Add this line before sourcing powerlevel10k in ~/.zshrc
+   typeset -g POWERLEVEL9K_TERM_SHELL_INTEGRATION=true
+   ```
+
+2. If issues persist, temporarily disable these tools in your shell configuration file (e.g., `~/.zshrc` for Zsh)
+3. If the issue resolves, gradually re-enable features to identify the conflicting component
+
+## Advanced Troubleshooting
+
+### Shell Integration Not Available
+
+Shell integration activation sequence (`\x1b]633;A\x07`) was not received. Shell integration features are disabled. Verify you are using a supported shell (Bash, Zsh, PowerShell, Fish) and shell integration is enabled in settings.
+
+### Command Stream Not Available
+
+Command stream failed: missing start sequence (`\x1b]633;C\x07`) or command already ended (`\x1b]633;D\x07`). Command output cannot be captured. Check if the command started correctly or has completed execution.
+
+### Verifying Shell Integration Status
+
+Run these commands to verify shell integration sequences are installed:
+
+#### Bash
+```bash
+# View all shell integration sequences
+set | grep -i '[16]33;'
+
+# Should show VSCode shell integration functions like:
+# printf '\e]633;E;%s;%s\a' - Command line set
+# printf '\e]633;C\a' - Command executed
+# printf '\e]633;D\a' - Command finished
+# printf '\e]633;B\a' - Command start
+# printf '\e]633;A\a' - Shell integration activated
+# printf '\e]633;P;Prompt=%s\a' - Prompt marker
+
+# Check for PROMPT_COMMAND and DEBUG trap
+echo "$PROMPT_COMMAND" | grep vsc
+trap -p DEBUG | grep vsc
+```
+
+#### Zsh
+```zsh
+# List all VSCode shell integration functions
+functions | grep -i vsc  # Should show __vsc_precmd, __vsc_preexec, etc.
+
+# Verify shell integration hooks are installed
+typeset -p precmd_functions preexec_functions  # Should include __vsc_precmd and __vsc_preexec
+
+# Check Powerlevel10k integration (if installed)
+(( ${+functions[p10k]} )) && typeset -p POWERLEVEL9K_TERM_SHELL_INTEGRATION  # Should show "true"
+```
+
+#### PowerShell
+```powershell
+# View shell integration functions
+Get-Command -Name "*VSC*" -CommandType Function
+
+# Check prompt function
+Get-Content Function:\Prompt | Select-String "VSCode"
+```
+
+#### Fish
+```fish
+# Check for shell integration functions
+functions | grep -i vsc
+
+# Verify fish_prompt and fish_preexec hooks
+functions fish_prompt | grep -i vsc
+functions fish_preexec | grep -i vsc
+```
+
+Visual indicators of active shell integration:
+1. Shell integration indicator in terminal title bar
+2. Command detection highlighting
+3. Working directory updates in terminal title
+4. Command duration reporting
+5. Exit code reporting for failed commands
+
+## Troubleshooting Terminal Execution Failures
+
+If commands that previously worked suddenly stop working:
+1. Close the current terminal
+2. Let Roo Code open a new terminal for you
+3. Try your command again
+
+This often resolves temporary shell integration issues. However, if you experience persistent terminal execution failures and can reliably reproduce the problem, please [open a ticket](https://github.com/RooVetGit/Roo-Code/issues/new) with:
+- A step-by-step reproduction of the problem
+- Your operating system and VSCode/Cursor version
+- The shell you're using (Bash, Zsh, PowerShell, Fish)
+- Any relevant error messages or terminal output
+
+This will help us investigate and fix the underlying issue.
+
+## Known Issues
+
+### Incomplete Terminal Output
+
+There is an ongoing issue in VSCode where terminal command output may not be completely captured by extensions like Roo Code. This can result in:
+- Missing portions of command output
+- Incomplete error messages
+- Delayed or missing command completion signals
+
+If you experience this issue, try:
+1. Closing and reopening the terminal
+2. Running the command again
+3. If the problem persists, you may need to manually copy-paste relevant output to Roo Code
+
+For detailed troubleshooting guidance, refer to the [Cline Wiki - Troubleshooting Shell Integration](https://github.com/cline/cline/wiki/Troubleshooting-%E2%80%90-Shell-Integration-Unavailable) guide.
+
+## Troubleshooting Resources
+
+- [VSCode Terminal Output Issue #237208](https://github.com/microsoft/vscode/issues/237208): Tracking the incomplete terminal output capture issue (ongoing as of March 8, 2025)
+- [VSCode Terminal Integration Test Repository](https://github.com/KJ7LNW/vsce-test-terminal-integration): A tool for validating shell integration functionality in your environment
+- [Cline Wiki - Troubleshooting Shell Integration](https://github.com/cline/cline/wiki/Troubleshooting-%E2%80%90-Shell-Integration-Unavailable): Comprehensive troubleshooting guide by Cline's original creator
+- [Shell Integration Improvements PR](https://github.com/cline/cline/pull/1089): Enhanced shell integration behavior (merged in Roo Code as of March 8, 2025, pending merge in Cline)
+- [Roo Code Shell Integration Architecture PR](https://github.com/RooVetGit/Roo-Code/pull/1365): Detailed discussion and proposed architectural changes for more reliable shell integration (pending as of March 8, 2025)
+
+## Support
+
+If you've followed these steps and are still experiencing problems, please:
+
+1. Check the [Roo Code GitHub Issues](https://github.com/RooVetGit/Roo-Code/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](https://discord.com/channels/1332146336664915968/1332212137568899162).
+
+_Content adapted from [Cline Wiki - Troubleshooting Shell Integration Unavailable](https://github.com/cline/cline/wiki/Troubleshooting-%E2%80%90-Shell-Integration-Unavailable)_
path: docs/shell-integration.md
user: login: ellipsis-dev[bot]
body: Please add a newline at the end of this file to conform with best practices.
created_at: 2025-03-09T01:11:04Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,326 @@
+# Terminal Shell Integration Guide
+
+## What is Shell Integration?
+
+Shell integration is a [new feature in VSCode 1.93](https://code.visualstudio.com/updates/v1_93#_terminal-shell-integration-api) that allows extensions like Roo Code to run commands in your terminal and read their output. Command output allows Roo Code to react to the result of the command on its 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 Roo Code to fix errors as the server logs them.
+
+## How Shell Integration Works
+
+Shell integration uses special terminal sequences (like ANSI escape codes) to mark different stages of command execution in your terminal. Here's how it works:
+
+1. **Activation**: When you open a terminal in VSCode, your shell sends an activation sequence (`\x1b]633;A\x07`) to initialize shell integration.
+
+2. **Command Lifecycle**: VSCode shell integration uses OSC (Operating System Command) sequence 633 to track each command's lifecycle:
+   - OSC 633 ; A - Mark prompt start
+   - OSC 633 ; B - Mark command start
+   - OSC 633 ; C - Mark command executed (pre-output)
+   - OSC 633 ; D [; `<exitcode>`] - Mark command finished with optional exit code
+   - OSC 633 ; E ; `<commandline>` [; `<nonce>`] - Explicitly set command line with optional nonce
+   - OSC 633 ; P ; `<Property>=<Value>` - Set properties like current working directory
+
+3. **Shell Integration Hooks**: Each shell uses specific hooks for different stages of command execution:
+
+   - Bash:
+     * Initial activation: `PROMPT_COMMAND` (sets up initial environment)
+     * Command start: `trap DEBUG` (triggers before command execution)
+     * Command stop: `PROMPT_COMMAND` (triggers after command completion)
+
+   - Zsh:
+     * Initial activation: `precmd` (sets up initial environment)
+     * Command start: `preexec` (triggers before command execution)
+     * Command stop: `precmd` (triggers after command completion)
+
+   - PowerShell:
+     * Initial activation: `prompt` function (sets up initial environment)
+     * Command input: `PSConsoleHostReadLine` (captures command input)
+     * Command start/stop: `prompt` function (handles both command start and completion)
+
+   - Fish:
+     * Initial activation: `fish_prompt` (sets up initial environment)
+     * Command start: `fish_preexec` (triggers before command execution)
+     * Command stop: `fish_prompt` (triggers after command completion)
+
+> **Note:** This hook implementation information was discovered through AI inspection of the VSCode source tree. If you find any inaccuracies, please submit a pull request with corrections.
+
+These hooks emit OSC (Operating System Command) sequences that VSCode recognizes to track:
+   - Prompt start/end positions
+   - Command start/execution/finish events
+   - Current working directory changes
+   - Command line content and execution status
+
+4. **Output Capture**: When a command runs, VSCode captures:
+   - Command text and working directory
+   - Start and end times
+   - Exit codes
+   - Output streams (stdout/stderr)
+
+This allows VSCode and extensions like Roo Code to:
+- Know exactly when commands start and finish
+- Capture command output reliably
+- Track command success/failure
+- Update the terminal UI with command status
+- React to command results automatically
+- Track the current working directory
+
+## How to Fix "Shell Integration Unavailable"
+
+### Step 1: Update VSCode or Cursor
+
+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
+
+### Step 2: Configure VSCode to Use the Correct Shell
+
+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.
+
+### Step 3: Restart VSCode
+
+After making these changes:
+
+1. Quit VSCode completely
+2. Reopen VSCode
+3. Start a new Roo Code session (you can resume your previous task and try to run the command again, this time with Roo Code being able to see the output)
+
+## Additional Troubleshooting for Windows Users
+
+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
+
+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](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"
+
+### PowerShell
+
+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](https://learn.microsoft.com/en-us/powershell/scripting/whats-new/migrating-from-windows-powershell-51-to-powershell-7?view=powershell-7.4#installing-powershell-7).
+
+#### Understanding PowerShell Execution Policies
+
+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](https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_execution_policies).
+
+#### Steps to Change the Execution Policy
+
+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:
+     ```powershell
+     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:
+     ```powershell
+     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.
+
+## Manual Shell Integration Installation
+
+If you're still experiencing issues after trying the basic troubleshooting steps, you can try manually installing shell integration:
+
+### Installation Instructions
+
+For Bash users:
+1. Run `code ~/.bashrc` in the terminal to open your bash configuration file.
+2. Add the following line to your `~/.bashrc`:
+```bash
+[[ "$TERM_PROGRAM" == "vscode" ]] && . "$(code --locate-shell-integration-path bash)"
+```
+
+For Zsh users:
+1. Run `code ~/.zshrc` in the terminal to open your zsh configuration file.
+2. Add the following line to your `~/.zshrc`:
+```bash
+[[ "$TERM_PROGRAM" == "vscode" ]] && . "$(code --locate-shell-integration-path zsh)"
+```
+
+For PowerShell users:
+1. Run `code $Profile` in the terminal to open your PowerShell profile.
+2. Add the following line to the file:
+```powershell
+if ($env:TERM_PROGRAM -eq "vscode") { . "$(code --locate-shell-integration-path pwsh)" }
+```
+
+For Fish users:
+1. Run `code ~/.config/fish/config.fish` in the terminal to open your fish configuration file.
+2. Add the following line to your `~/.config/fish/config.fish`:
+```fish
+string match -q "$TERM_PROGRAM" "vscode"; and . (code --locate-shell-integration-path fish)
+```
+
+### About the Shell Integration Path Command
+
+The `code --locate-shell-integration-path` command returns the path to shell-specific integration scripts. It supports four shell types:
+- bash - returns path to `shellIntegration-bash.sh`
+- zsh - returns path to `shellIntegration-rc.zsh`
+- pwsh - returns path to `shellIntegration.ps1`
+- fish - returns path to `shellIntegration.fish`
+
+Any other value will throw an error: "Error using `--locate-shell-integration-path`: Invalid shell type".
+
+## Unusual Terminal Output
+
+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. If using Powerlevel10k, you must set `typeset -g POWERLEVEL9K_TERM_SHELL_INTEGRATION=true` in your `~/.zshrc` before sourcing the theme. This enables proper integration with VSCode's shell integration, which differs from the integration provided by VSCE.
path: docs/shell-integration.md
user: login: ellipsis-dev[bot]
body: In the unusual terminal output section, 'VSCE' appears to be a typo. Please update it to 'VSCode' for consistency.
```suggestion
- Powerlevel10k: A zsh theme that adds visual elements to the prompt. If using Powerlevel10k, you must set `typeset -g POWERLEVEL9K_TERM_SHELL_INTEGRATION=true` in your `~/.zshrc` before sourcing the theme. This enables proper integration with VSCode's shell integration, which differs from the integration provided by VSCode.
```
created_at: 2025-03-09T01:11:04Z
author_association: CONTRIBUTOR
diff_hunk: @@ -112,7 +112,7 @@ Yes, if you are using a provider with a model that support web browsing. Be mind
 
 ### Can Roo Code run commands in my terminal?
 
-Yes, Roo Code can execute commands in your VS Code terminal.  You will be prompted to approve each command before it's executed, unless you've enabled auto-approval for commands. Be extremely cautious about auto-approving commands.
+Yes, Roo Code can execute commands in your VS Code terminal.  You will be prompted to approve each command before it's executed, unless you've enabled auto-approval for commands. Be extremely cautious about auto-approving commands. If you're experiencing issues with terminal commands, see the [Shell Integration Guide](shell-integration) for troubleshooting.
path: docs/faq.md
user: login: mrubens
body: I think you’ll need to update this link to /troubleshooting/shell-integration
created_at: 2025-03-09T01:35:29Z
author_association: COLLABORATOR
diff_hunk: @@ -112,7 +112,7 @@ Yes, if you are using a provider with a model that support web browsing. Be mind
 
 ### Can Roo Code run commands in my terminal?
 
-Yes, Roo Code can execute commands in your VS Code terminal.  You will be prompted to approve each command before it's executed, unless you've enabled auto-approval for commands. Be extremely cautious about auto-approving commands.
+Yes, Roo Code can execute commands in your VS Code terminal.  You will be prompted to approve each command before it's executed, unless you've enabled auto-approval for commands. Be extremely cautious about auto-approving commands. If you're experiencing issues with terminal commands, see the [Shell Integration Guide](shell-integration) for troubleshooting.
path: docs/faq.md
user: login: KJ7LNW
body: good  catch 
created_at: 2025-03-09T01:43:39Z
author_association: CONTRIBUTOR
diff_hunk: @@ -112,7 +112,7 @@ Yes, if you are using a provider with a model that support web browsing. Be mind
 
 ### Can Roo Code run commands in my terminal?
 
-Yes, Roo Code can execute commands in your VS Code terminal.  You will be prompted to approve each command before it's executed, unless you've enabled auto-approval for commands. Be extremely cautious about auto-approving commands.
+Yes, Roo Code can execute commands in your VS Code terminal.  You will be prompted to approve each command before it's executed, unless you've enabled auto-approval for commands. Be extremely cautious about auto-approving commands. If you're experiencing issues with terminal commands, see the [Shell Integration Guide](shell-integration) for troubleshooting.
path: docs/faq.md
user: login: KJ7LNW
body: done 
created_at: 2025-03-09T01:44:30Z
author_association: CONTRIBUTOR

PR comments:
user: login: KJ7LNW
created_at: 2025-03-09T01:32:15Z
body: > Content is great, but I don’t think this should be a top-level page. Can you put it under a Troubleshooting category (directory and in the sidebar) and update the links? Thank you!

done 
author_association: CONTRIBUTOR
user: login: KJ7LNW
created_at: 2025-03-09T01:46:45Z
body: awesome. when does this land on docs site ?
author_association: CONTRIBUTOR
user: login: mrubens
created_at: 2025-03-09T01:49:18Z
body: > awesome. when does this land on docs site ?

Should be there now! https://github.com/RooVetGit/Roo-Code-Docs/actions/runs/13743605731
author_association: COLLABORATOR
user: login: KJ7LNW
created_at: 2025-03-09T03:45:16Z
body: g2g, thanks!
author_association: CONTRIBUTOR