[BUG] The Roo code tries to run a Unix shell command, but does not understand that I am working in Windows.

[AlexNek]

Problem (one or two sentences)

Most error using of "&&" in terminal command after error messages try to skip command sometimes try to use Most errors occur when using '& &' in a terminal command. After an error message, try skipping the command. Sometimes try using PowerShell. But it mostly skips over it and never remembers that I use Windows. Why not check the OS type at the beginning?

Context (who is affected and when)

Any run that requires a shell command.

Reproduction steps

Don't know exact prompt. Roo code call shell command sometimes, for example build application.
cd path && call build -- not for windows

Expected result

generated shell command syntax must depends from used OS

Actual result

always generate unix shel command by default

Variations tried (optional)

No response

App Version

3.37.1

API Provider (optional)

None

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

The system already correctly detects and reports the OS and default shell in the system prompt via the SYSTEM INFORMATION section. However, the RULES section contains a Unix-specific example using && for command chaining (in src/core/prompts/sections/rules.ts), which is not compatible with Windows shells:

• PowerShell: Uses ; for command separation, or can continue using && in PowerShell 7+
• cmd.exe: Uses & (single ampersand) for command chaining

Proposed Fix

1. Modify src/core/prompts/sections/rules.ts to make the command chaining example shell-aware:

   • Detect the current platform and shell
   • Use the appropriate syntax in the example (&& for Unix/Git Bash, ; for PowerShell, & for cmd.exe)
   • Add a note explaining the different syntaxes for different shells

2. Update the execute_command tool descriptions in both:

   • src/core/prompts/tools/execute-command.ts
   • src/core/prompts/tools/native-tools/execute_command.ts

   To include examples for different shells so the model better understands platform-specific syntax.

3. Add tests to verify the shell-specific examples are generated correctly for each platform.

This approach ensures the model receives platform-appropriate examples while maintaining the existing OS/shell detection infrastructure.

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