You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi vscode team, thanks for providing such a useful feature as vscode remote tunnel. I've been using vscode remote tunnel on multiple machines recently, and two of them created tunnels with the same name (they both had names like node-*), which caused some confusion. Although I discovered that I can specify the name of the tunnel with the --name parameter, I found that there is no other place to change the name of the created tunnel, and I can only connect to the tunnel or unregister the tunnel in the Remote Explorer, can you please consider to add the function of renaming the tunnel in the future?
Thanks again for providing vscode remote tunnel, it's a great feature!
The text was updated successfully, but these errors were encountered:
WhenMelancholy
changed the title
Hopefully it will be possible to rename the tunnel that has been created
Request to rename the tunnel that has been created
May 10, 2024
Hi vscode team, thanks for providing such a useful feature as vscode remote tunnel. I've been using vscode remote tunnel on multiple machines recently, and two of them created tunnels with the same name (they both had names like node-*), which caused some confusion. Although I discovered that I can specify the name of the tunnel with the --name parameter, I found that there is no other place to change the name of the created tunnel, and I can only connect to the tunnel or unregister the tunnel in the Remote Explorer, can you please consider to add the function of renaming the tunnel in the future?
Thanks again for providing vscode remote tunnel, it's a great feature!
The text was updated successfully, but these errors were encountered: