Integrations
Open VSX Extensions
OPIDE uses Open VSX — the open-source extension registry — not the proprietary VS Code Marketplace. No gatekeeping, no Microsoft dependency, thousands of compatible extensions.
Open VSX vs VS Code Marketplace#
The VS Code Marketplace is proprietary and only officially available to Microsoft-affiliated editors. Extensions published there cannot legally be redistributed in other editors without Microsoft's permission.
Open VSX (open-vsx.org) is a vendor-neutral, open-source alternative run by the Eclipse Foundation. Any editor can use it, any publisher can list there, and the extension format is compatible with VS Code extensions. OPIDE uses Open VSX exclusively.
Installing extensions#
Open the Extensions panel from the sidebar or with Cmd+Shift+X. Search the Open VSX registry directly from inside OPIDE. Click Install. The extension downloads, installs, and activates without a restart in most cases.
Extension security#
Extensions run in OPIDE's extension sandbox. The runtime implementation enforces the same principle as the agent sandbox — extensions declare what capabilities they need, and the host grants only those capabilities.
- ◆Extensions cannot access the filesystem outside declared paths
- ◆Extensions cannot make network requests to undeclared hosts
- ◆Extension code runs in a separate process from the OPIDE engine
- ◆A misbehaving extension cannot crash or corrupt the OPIDE session
Building extensions for OPIDE#
OPIDE is compatible with the VS Code extension API surface. Extensions built for VS Code that use standard APIs will run in OPIDE without modification in most cases. Extensions that use proprietary VS Code APIs or call into VS Code internals will not work.
To publish an extension for OPIDE users, publish it to Open VSX. The process is straightforward — create a publisher account at open-vsx.org, then use ovsx publish from the command line.