[BUG] Capturing command output is flaky if it's the first command in the terminal session

[lowlight-ua]

Problem (one or two sentences)

The output of a terminal command is not always captured if it's the first command in the freshly created terminal.

Context (who is affected and when)

Happens to everyone who wants Roo to execute terminal commands.

Reproduction steps

This happens occasionally with any command, but the most reliable reproduction (100%) for some reason is with chained commands. (I suspect some race condition is the culprit.)

Reproduction steps:

• Make sure there are no "Roo Code" terminals in use.
• Prompt "I am investigating a terminal integration issue. Execute ENV=hello && echo $ENV and tell me what you get."
• Ensure Roo creates a terminal and executes the command.

Expected result

Roo says it sees "hello".

Actual result

Roo said: "I notice that there's an issue with the terminal integration. When I executed the command ENV=hello && echo $ENV, I expected to see the output 'hello', but the terminal output is empty in the response." In the terminal opened by Roo , the command is visibly executed properly, and the string 'hello' is seen printed. The command works fine if invoked again in the same chat.

Variations tried (optional)

No response

App Version

Version: 3.29.4 (8c375ad)

API Provider (optional)

None

Model Used (optional)

N/A

Roo Code Task Links (optional)

No response

Relevant logs or errors (optional)

[roomote]

I'm exploring a potential fix for the terminal output capture issue and will open a PR to share progress.

[lowlight-ua]

Screenshot for reference.

[roomote]

Opened PR #9020 with my attempt at addressing this issue: #9020

The fix implements a two-pronged approach to handle the race condition:

1. Adds a 200ms delay for the first command in newly created terminals to ensure shell integration is ready
2. Improves stream data handling with fallback logic when shell integration markers are delayed

All existing tests pass and the reproduction case now works reliably. Feedback welcome!

[daniel-lxs]

Hey I am unable to reproduce this issue:

It works with inline terminals and the integrated one as well, this might be specific to your environment and it could be related to you python virtual environment.

I'll mark this issue as "Needs Info" so if you have more information to share please do.