Skip to content

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.

Open Plugin Manager → Marketplace, install RDP or VNC, and enable it. These are separate plugins; install only the protocols you need. Connection profiles and the viewer remain in OxideTerm, while the plugin provides the protocol engine.

If the required plugin is missing or disabled, the connection form shows its status. Opening the connection provides a shortcut to the marketplace or plugin management. A saved or cloud-synchronized profile still needs the corresponding plugin installed on the current device before it can connect.

Open New Connection and choose RDP or VNC.

ProtocolDefault portConnection details
RDP3389Host, port, username, and password
VNC5900Host 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.

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.

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.

RDP plugin 0.2.0 requires OxideTerm 2.2.5 or later. Update both when using its display-layout fixes.

In single-monitor mode, Follow window size requests a remote resolution based on the viewer area. The resolution menu also offers fixed sizes. In all-monitor mode, the remote layout follows the active physical monitors; resizing the app changes local fitting, not the remote monitor topology. Connecting or disconnecting an external display, closing a laptop’s internal screen, and reconnecting can change that layout.

The menu’s current remote size is not necessarily your display’s advertised resolution: sidebars, window borders, scaling, and multi-monitor layout affect the available area. If an edge or desktop panel is missing, compare a screenshot taken on the remote desktop with the viewer and record the menu’s remote size, display mode, and active local monitors. A panel present in the remote screenshot but missing locally points to a display-layout or viewport issue rather than a missing remote panel.

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.