Hey, thanks for the detailed report. This is really helpful.
This is a known regression related to parsing Windows paths in Remote SSH sessions. The root cause is a UriError that happens when the agent tries to resolve file paths over an SSH connection to a Windows host. This has been reported a few times already, and it tends to come back in different versions.
Temporary workaround: try switching the bottom panel from Terminal to Output before running agent commands. In some cases this prevents the path parsing issue because the terminal context does not get collected.
Related threads:
- Agent connection error - remote SSH - when console open
- [URGENT] Agent stops working after the first message
A few questions to narrow it down:
- When Write/StrReplace crashes, do you see a
UriErrorin the devtools console (Help > Toggle Developer Tools > Console tab)? - Is the Terminal panel open or visible when the error happens?
- Which Remote SSH extension are you using, Anysphere or Microsoft? (
CMD+Shift+X> search “Remote-SSH” > check the publisher)
The team is aware of this issue. Let me know if the Output panel workaround changes anything.