Deploying the OX IDE Extension with MDM
Organizations that centrally manage developer workstations can deploy the OX IDE extension across all managed devices using a Mobile Device Management (MDM) solution instead of requiring each developer to install and configure the extension individually.
This deployment method is intended for IT administrators and security teams that want to standardize IDE security across the organization, reduce manual setup, and simplify onboarding. In addition to installing the extension, the deployment can automatically configure the OX API key so developers can start using the extension immediately without performing additional configuration.
The installer supports unattended deployment through MDM platforms such as Jamf, Microsoft Intune, Kandji, and other MDM solutions capable of distributing files and running scripts.
Supported IDEs
The deployment process supports the following VS Code-based IDEs:
Visual Studio Code
Yes
Cursor
Yes
Windsurf
Yes
VSCodium
Yes
Supported operating systems
macOS
install-ox-extension.sh
Linux
install-ox-extension.sh
Windows
install-ox-extension.ps1
How the installer works
For each supported IDE detected on a device, the installer:
Installs the OX IDE extension.
Configures the OX API key, if provided.
Preserves the user's existing IDE settings.
Skips IDEs that are not installed.
Can safely be run multiple times without affecting existing installations.
If a local VSIX package is provided, the installer uses it. Otherwise, it attempts to install the extension from the appropriate marketplace.
Recommended deployment method
OX recommends deploying the extension together with the VSIX installation package.
Using a VSIX package provides a consistent installation experience across all supported IDEs and does not depend on marketplace availability or internet connectivity. This approach is the most reliable option for organizations that use multiple VS Code-based IDEs or operate in restricted environments.
Installing the extension directly from the marketplace is supported for Visual Studio Code but may not be available for other supported IDEs.
Before you begin
Before the deployment process, make sure you have the following files:
install-ox-extension.sh
Installer script for macOS and Linux, see Deployment scripts.
install-ox-extension.ps1
Installer script for Windows, see Deployment scripts.
OX IDE Extension .vsix package (recommended)
Installs the OX IDE extension locally without relying on marketplace availability. Recommended for consistent deployment across all supported IDEs.
Download a VSIX package
If the target machine does not have Internet access or cannot reach the Visual Studio Code Marketplace, download the extension as a VSIX package on another machine and transfer it to the target machine.
To download the VSIX package:
Open Visual Studio Code on a machine that has access to the Visual Studio Code Marketplace.
Select OX Security extension from the activity bar or by pressing:
Ctrl+Shift+X on Windows and Linux.
Cmd+Shift+X on macOS.
Search for the extension that you want to download.

In the search results, right-click the extension and select Download VSIX.
Choose a destination folder and save the
.vsixfile.Transfer the
.vsixfile to the target machine.
Deploy on macOS or Linux
Distribute the installer script and, optionally, the VSIX package to the target devices using your MDM solution.
Make the installer executable:
Run the installer:
Installer options
--api-key <KEY>
Configures the OX API key for the extension. If omitted, the extension is installed without configuring authentication.
--vsix <PATH>
Installs the extension from the specified VSIX package. If omitted or unavailable, the installer attempts to install the extension from the marketplace.
--ext-id <ID>
Overrides the default extension identifier (oxsecurity.ox-ide).
Deploy on Windows
Distribute the installer script and, optionally, the VSIX package to the target devices using your MDM solution.
Run the installer:
Installer options
-ApiKey <KEY>
Configures the OX API key for the extension. If omitted, the extension is installed without configuring authentication.
-Vsix <PATH>
Installs the extension from the specified VSIX package. If omitted or unavailable, the installer attempts to install the extension from the marketplace.
-ExtId <ID>
Overrides the default extension identifier (oxsecurity.ox-ide).
Exit codes
The installer returns one of the following exit codes, which can be used by your MDM solution to verify deployment status.
0
At least one supported IDE was successfully provisioned, or no supported IDE was found on the device.
1
Invalid arguments were supplied or the operating system is not supported.
2
One or more supported IDEs were found, but none could be successfully provisioned.
After deployment
Restart the IDE, or reload the IDE window, before the newly installed extension and any configured API key become available.
Deployment Scripts
Last updated
