[BUG] unicode/charset conversion, terminal command-line

[drzraf]

Problem (one or two sentences)

When Claude runs the python interpret with an inline command containing an UTF-8 character, it trigger an error in Codium's terminal

Running

python3 << 'EOF'
print(" → foo")

EOF

SyntaxError: Non-UTF-8 code starting with '\x86' in file <stdin> on line 1, but no encoding declared; see https://peps.python.org/pep-0263/ for details

Copy/pasted in my regular terminal, it just works, so it's about roo-code passing (or the terminal receiving) the command-line that something weird happens.

Same with command as an argument (below screenshot)

Context (who is affected and when)

Running a UTF-8 commands in the terminal

Reproduction steps

1. Input the following:

Run python -c 'print(" → foo")'

Expected result

The command runs

Actual result

bad charset conversion garble the command line (or the Python code)

Variations tried (optional)

No response

App Version

0.0.6975

API Provider (optional)

Anthropic

Model Used (optional)

claude-4.5-sonnet

Roo Code Task Links (optional)

No response

Relevant logs or errors (optional)

Nothing in apparmor's log (codium is heavily sandbox)

But I don't see any obvious reason an otherwise functioning embedded terminal would experience this specific charset problem.

[roomote]

I'm exploring a potential fix for the UTF-8 encoding issue with terminal commands. I'll investigate why special characters are being incorrectly encoded when passed to the terminal and open a PR to share progress.

[roomote]

Opened PR #8939 with my attempt at addressing this UTF-8 encoding issue. The fix adds LANG and LC_ALL environment variables set to en_US.UTF-8 to ensure proper handling of special characters in terminal commands. All CI checks are passing. Feedback welcome!

PR link: #8939

[daniel-lxs]

Unable to reproduce this issue on macOS with UTF-8 locale. Tested the exact commands from the issue and all UTF-8 characters work correctly.

The error (Non-UTF-8 code starting with '\x86') indicates character encoding corruption specific to your VSCodium + Linux + apparmor environment. Roo Code passes commands directly to the terminal - encoding is handled by VSCode/VSCodium and your system.

This appears to be an environment-specific configuration issue rather than a bug in the extension. Closing as not reproducible.