When connecting to a remote host using codeium.windsurf-remote-openssh, the extension automatically opens a terminal panel.
This behavior is disruptive because:
- The terminal steals focus from the editor
-
- It reopens even after being manually closed
-
-
- It appears to be triggered not only on initial connection but also during reconnection attempts
-
-
-
- There is currently no configuration option to disable this behavior.
Expected behavior:
Provide a setting to prevent the terminal from opening automatically on SSH connection and reconnection events.
Example:
"remote.windsurfSSH.showTerminalOnConnect": false
Additional context:
The issue persists regardless of standard VS Code settings such as:
terminal.integrated.showOnMount
-
terminal.integrated.defaultLocation
The behavior seems to be hardcoded in the extension
Reconnection logic (maxReconnectionAttempts) may also trigger the terminal repeatedly
Environment:
- Windsurf (latest)
-
- Extension:
codeium.windsurf-remote-openssh
Impact:
This negatively affects developer experience, especially for users who frequently reconnect or work with multiple SSH sessions.
Suggestion:
Expose a setting to control:
- Auto-open terminal on connect
-
- Auto-open terminal on reconnect
-
-
- Optional: run SSH process silently in background
When connecting to a remote host using
codeium.windsurf-remote-openssh, the extension automatically opens a terminal panel.This behavior is disruptive because:
Expected behavior:
Provide a setting to prevent the terminal from opening automatically on SSH connection and reconnection events.
Example:
Additional context:
The issue persists regardless of standard VS Code settings such as:
terminal.integrated.showOnMountterminal.integrated.defaultLocationThe behavior seems to be hardcoded in the extension
Reconnection logic (
maxReconnectionAttempts) may also trigger the terminal repeatedlyEnvironment:
codeium.windsurf-remote-opensshImpact:
This negatively affects developer experience, especially for users who frequently reconnect or work with multiple SSH sessions.
Suggestion:
Expose a setting to control: