BUG: `execute_command` Tool Incorrectly Encodes `&&` as `&&`

[neno-is-ooo]

App Version

3.10.5

API Provider

Google Gemini

Model Used

2.5 pro

Actual vs. Expected Behavior

Actual Behavior:
From time to time, when requesting the execution of a shell command containing the && operator for command chaining via the execute_command tool, the tool appears to incorrectly XML-encode the && as && before passing it to the shell. This results in a shell parse error.

Expected Behavior:
The command string provided within the <command> tag of the execute_command tool should be passed directly to the user's shell without unintended XML encoding of shell metacharacters like &&. The shell should receive && literally to correctly interpret it as a command chaining operator.

Detailed Steps to Reproduce

1. Request the execution of a chained shell command using &&. For example:

   rm -rf some_directory && python some_script.py

2. Use the execute_command tool with the command string:

Relevant API Request Output

Additional Context

No response

[edgan]

I have seen this too.

[mrubens]

Fix coming in the next release

[mrubens]

Try 3.11.0 and reopen if it's still an issue. Thank you!