- Notifications
You must be signed in to change notification settings - Fork35
Open
Assignees
Description
Description:
The current implementation for retrieving Remote - SSH channel logs returnsundefined for non-Microsoft VS Code forks.
vscode-coder/src/remote/remote.ts
Lines 898 to 905 in118d50a
| constlatestOutput=dirs | |
| .reverse() | |
| .filter((dir)=>dir.startsWith("output_logging_")); | |
| if(latestOutput.length===0){ | |
| returnundefined; | |
| } | |
| constdir=awaitfs.readdir(path.join(upperDir,latestOutput[0])); | |
| constremoteSSH=dir.filter((file)=>file.indexOf("Remote - SSH")!==-1); |
Issue:
VS Code forks use different extension identifiers for Remote SSH:
- Cursor:
anysphere.remote-ssh - Google Antigravity:
google.antigravity-remote-openssh - Other forks: Likely affected as well
These forks storeRemote - SSH logs in folders matching their extension names rather than the standard Microsoft folder structure. The log files still contain "Remote - SSH" in their filenames.
Solution:
The log retrieval logic should check for fork-specific extension folders when searching for Remote - SSH logs.
Metadata
Metadata
Assignees
Labels
No labels