[BUG] First use of terminal fails with conda

[alippai]

Problem (one or two sentences)

When there is a first command upon activating the terminal (eg conda activate automatically), then the output of the roo executed command is lost. It doesn't wait for the output of the actual command

Context (who is affected and when)

Users during a terminal command execution (when using vscode's terminal set up with conda auto activation)

Reproduction steps

1.) Ask roocode to execute a terminal command
2.) The output is not wait

Expected result

The output is wait and processed by roo

Actual result

Output is skipped, Roo is confused

Variations tried (optional)

No response

App Version

3.46.1

API Provider (optional)

OpenAI Compatible

Model Used (optional)

No response

Roo Code Task Links (optional)

No response

Relevant logs or errors (optional)

[roomote]

I've analyzed this issue and here's my proposed implementation plan:

Root Cause Analysis

When a terminal is created with conda auto-activation (or any shell initialization that runs commands), the following race condition can occur:

1. Terminal is created
2. Conda activation starts running automatically (triggered by shell init scripts)
3. Shell integration becomes available
4. Roo's command is triggered via executeCommand()
5. VSCode fires onDidStartTerminalShellExecution events for BOTH conda activation and Roo's command

The current implementation in TerminalRegistry.ts blindly sets the stream when onDidStartTerminalShellExecution fires, without verifying that the execution event corresponds to the command Roo is actually running. This can cause Roo to pick up the wrong stream (conda's) and miss its own command's output.

Proposed Fix

1. Add command verification in setActiveStream()

Modify BaseTerminal.setActiveStream() to accept an optional eventCommand parameter and verify it matches the process's expected command before emitting stream_available.

2. Update TerminalRegistry.onDidStartTerminalShellExecution

Pass the command from e.execution?.commandLine?.value to setActiveStream() for verification.

3. Flexible command matching

Since commands might be modified (e.g., PowerShell counter workaround appends extra commands), use a flexible matching approach:

• Check if the process's command is a prefix of the event command
• Or if they share a common substantial substring
• Log warnings when matches fail for debugging

Files to modify:

• src/integrations/terminal/BaseTerminal.ts - Add command parameter and verification to setActiveStream()
• src/integrations/terminal/TerminalRegistry.ts - Pass command from event to setActiveStream()

Benefits:

• Prevents conda/other auto-activation commands from interfering with Roo's command execution
• Maintains backwards compatibility (if no command provided, behaves as before)
• Adds logging for debugging edge cases

Please mention @roomote in a comment saying that you approve this plan, and I'll proceed with the implementation.

[alippai]

@roomote approved

[roomote]

Thanks for the approval! I've seen your comment and will proceed with implementing the fix. I'll open a PR to share progress.

[roomote]

Opened PR #11149 with my attempt at addressing this. The fix adds command verification when setting the terminal stream, so conda/pyenv/other auto-activation commands won't hijack the stream meant for Roo's actual command. Feedback welcome!

[mini2s]

Problem (one or two sentences)

When there is a first command upon activating the terminal (eg conda activate automatically), then the output of the roo executed command is lost. It doesn't wait for the output of the actual command

Context (who is affected and when)

Users during a terminal command execution (when using vscode's terminal set up with conda auto activation)

Reproduction steps

1.) Ask roocode to execute a terminal command 2.) The output is not wait

Expected result

The output is wait and processed by roo

Actual result

Output is skipped, Roo is confused

Variations tried (optional)

No response

App Version

3.46.1

API Provider (optional)

OpenAI Compatible

Model Used (optional)

No response

Roo Code Task Links (optional)

No response

Relevant logs or errors (optional)

vscode config

zgsm-ai#591

[alippai]

@mini2s i need the shell activation commands, without them the roo commands execution fails (eg wrong python env used)