Remote Desktop
OxideTerm opens RDP and VNC as native desktop tabs alongside terminals and files. The desktop protocol has its own login credentials; an optional saved SSH gateway provides the network route.
Create a Connection
Section titled “Create a Connection”Open New Connection and choose RDP or VNC.
| Protocol | Default port | Connection details |
|---|---|---|
| RDP | 3389 | Host, port, username, and password |
| VNC | 5900 | Host and port; authentication depends on the server |
Save a profile to reopen or edit it in Session Manager, or connect temporarily. The command palette also accepts rdp://host and vnc://host, with an optional explicit port.
SSH Gateway
Section titled “SSH Gateway”Choose a saved SSH connection as the gateway when the desktop host is reachable through it. OxideTerm establishes a managed tunnel to the desktop endpoint through that SSH connection. The selected gateway can use its configured jump-host chain and authentication.
Gateway authentication and RDP/VNC authentication remain separate. The desktop tab retains the tunnel while it needs it; closing the tab releases that consumer without disconnecting other users of the shared SSH connection.
RDP SOCKS5 Proxy
Section titled “RDP SOCKS5 Proxy”For an RDP connection without an SSH gateway, choose direct access, the global proxy, or a custom SOCKS5 proxy in the profile editor. Supported proxy settings include authentication, remote DNS, and bypass rules. HTTP CONNECT is not supported for this RDP route.
When an SSH gateway is selected, the gateway’s own route and proxy settings are used; the RDP proxy is not applied again to the local tunnel. Route settings are retained in Session Manager and supported cloud-synchronized profiles. Password synchronization is a separate opt-in choice; see Connections & Sessions.
During a Session
Section titled “During a Session”Remote desktop tabs handle keyboard and pointer input, remote cursors, clipboard exchange, and viewport resizing where the server and provider support them. Per-profile options control supported redirection and display behavior.
Use the tab controls to reconnect or close the desktop. Reconnecting starts a fresh protocol session after the previous helper exits.
For Linux GUI applications in a local Windows Subsystem for Linux distribution, see WSL Graphics. It is a separate Windows-only VNC-backed workflow.