serverInstallPath doesn't allow '@' for the directory path

[geniusAhua]

Is there an existing issue for this bug?

• I have searched the existing open issues and found none that apply.
• If I find any issue of interest that is related or closed, I will included a link to it in this issue.

Required Troubleshooting Steps

• I have read and performed the troubleshooting steps
• I have tried both values of the remote.SSH.useLocalServer setting
• My issue was not covered in the Tips and Tricks linked from the Troubleshooting Wiki.
• I will include a complete copy of my Remote - SSH logs by running Remote-SSH: Show Log in the command palette or from View > Output in the menu bar

[Optional] Diagnose with Copilot

I did not ask the @remote-ssh participant for help

In step 2 of the troubleshooting wiki, what was the result of running the generated SSH command verbatim outside of VS Code?

I did not try step 2 of the troubleshooting steps

Remote-SSH Log

Remote-SSH Log

[PASTE LOG HERE WITHIN THE BACKTICKS TO FORMAT]

Expected Behavior

If there is a '@' in the path, the plugin can't apply it correctly, when I want to set the serverInstallPath.
However, for the previous version, like 0.101.2023032715, it can apply a path with '@' correctly.

Actual Behavior

Output an error log.

Steps To Reproduce

1. version: 0.118.2025021215
2. set a path with '@' for serverInstallPath
3. connect that server
4. it will show that error log

Anything else?

No response

[joshspicer]

Thanks for the feedback. That change was made a few months ago, restricting most special characters, are not currently supported in the path name to ensure wide compatibility with different OSs/filesystems/etc.

If there's additional reasons to allow this character that we aren't currently considering, please do let us know

[vs-code-engineering]

We closed this issue because we don't plan to address it in the foreseeable future. If you disagree and feel that this issue is crucial: we are happy to listen and to reconsider.

If you wonder what we are up to, please see our roadmap and issue reporting guidelines.

Thanks for your understanding, and happy coding!