Skip to content

Commit b3cc150

Browse files
committed
docs: add troubleshooting section for Python virtual environment issues in shell integration
1 parent e3b193c commit b3cc150

File tree

1 file changed

+15
-0
lines changed

1 file changed

+15
-0
lines changed

docs/features/shell-integration.md

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -446,6 +446,21 @@ This setup works reliably on Windows systems using Cygwin, Fish, and the Starshi
446446
**Issue**: Sometimes VS Code doesn't show or capture all the output from a command.
447447
448448
**Workaround**: If you notice missing output, try closing and reopening the terminal tab, then run the command again. This refreshes the terminal connection.
449+
450+
### Python Virtual Environment (venv) Issues
451+
452+
**Issue**: Disabling shell integration will disable venv; venv is VSCode-managed, Roo does not know anything about it because disabling shell integration uses a completely different mechanism for running commands (execa).
453+
454+
**Workaround**: If you need to use Python virtual environments with Roo Code, you might be able to:
455+
456+
```bash
457+
killall code # closes all vscode windows!
458+
. venv/bin/activate
459+
code
460+
```
461+
462+
This way the environment is configured before code launches so Roo should inherit it.
463+
449464
---
450465
451466
## Troubleshooting Resources

0 commit comments

Comments
 (0)