Plugins
Open Plugin Manager → Marketplace to install the features you need, then enable them in the plugin manager. RDP and VNC remote desktop support is provided by separate plugins; after installation, use New Connection or Session Manager to open a desktop. See Remote Desktop.
The plugin manager also handles updates, settings, permissions, and removal. Install plugins on each device where you need them; synchronizing connection profiles does not install their plugins.
Features Available Through Plugins
Section titled “Features Available Through Plugins”| Feature | What to install | Where to use it |
|---|---|---|
| Mosh sessions | Mosh | New Connection → Mosh; the server also needs mosh-server |
| Additional code languages | The matching language plugin | IDE and code previews |
| PDF pages | PDF Preview | File Manager and SFTP previews |
| SQLite tables | SQLite Preview | Read-only file previews |
| Certificate inspection | Certificate Viewer | PEM / DER certificate previews |
Runtime Model
Section titled “Runtime Model”Supported runtime kinds are:
processfor an executable managed by the host over versioned JSON Lines.wasmfor a Wasm module managed by the integrated runtime.manifest-onlyfor contributions that need no executable runtime.remote-desktopfor trusted protocol helpers used by the native RDP/VNC viewer.language,acp,terminal-transport, andhelperfor language support, AI agents, terminal transports, and managed helper programs.
Legacy JavaScript entries are not executed by the native application.
Installing and managing plugins
Section titled “Installing and managing plugins”The marketplace selects the highest release compatible with your app version and platform. A newer incompatible version shows its requirements without replacing the installed plugin. Incompatible installed plugins retain files and settings but do not activate. If an update is missing, refresh the marketplace and check its required app version; older clients using the frozen v1 catalog need an app upgrade to discover newer releases.
Plugins can also provide saved connection types and live workbenches. Supported profiles and credentials participate in encrypted export and cloud sync; running instances do not. Install the provider on each destination device. Updating or disabling a connection provider stops its instances while keeping saved profiles.
Use the desktop Plugin Manager to browse, install, enable, disable, update, and configure plugins. For local development, place a package under the active configuration directory:
<config-dir>/plugins/<plugin-id>/├── plugin.json└── plugin.wasm or bin/<executable>Run oxideterm paths --json to inspect the active configuration directory. The CLI can list, enable, disable, and inspect plugin settings; installation and updates belong to the desktop manager.
Contributions
Section titled “Contributions”Plugins can declare tabs, sidebar panels, settings, commands, keybindings, context menus, status items, terminal hooks, event subscriptions, AI tools, and supported transports. Tabs and panels provide declarative schemas; GPUI owns rendering and interaction.
Security
Section titled “Security”The host validates manifests and paths, passes the effective capabilities and allowed host APIs during activation, and keeps plugin diagnostics separate from protocol output. Review a plugin’s identity, permissions, settings, and declared surfaces before enabling it.
WASM guests use mediated host capabilities. Native process plugins and protocol helpers have operating-system process access and are not isolated by the WASM sandbox.
Next step
Section titled “Next step”Read the Plugin Development Guide for a native manifest and runtime walkthrough.