Hey, thanks for the detailed report, especially the breakdown of the Korean encoding cascade. That’s really helpful.
The main URI error is a known regression when connecting over SSH to a Windows host. The agent mishandles Windows style paths (C:\...) while collecting terminal context, which breaks file tools, diffs, and the Accept/Reject UI.
Same root cause as these threads:
- A path resolution error occurs when using an SSH remote environment
- Agent connection error - remote SSH - when console open
- Write and StrReplace tools return "Invalid arguments" when workspace is opened via Remote-SSH (Mac → Windows)
Temporary workaround (partial): switch the bottom panel from Terminal to Output before using the agent. This prevents terminal context collection, which is what triggers the URI error. It doesn’t always help for Windows to Windows SSH, but it’s worth a try.
Version rollback: going back to version 2.2.44 helped other users in this situation, though that’s not ideal long term.
The team is aware of the URI path parsing issue. The PowerShell encoding issues you described with CP949 and a Korean locale
A couple things that would help:
- Can you share the Request ID? (chat menu in the top right, then Copy Request ID)
- What version of the Anysphere Remote SSH extension are you on? (
Ctrl+Shift+X, search for Remote-SSH, then check the version number)
Let me know if the Output panel workaround changes anything for you.