Skip to main content

​
Overview

The scripts are designed to be executed on end-user devices through your MDM (Mobile Device Management) platform. They configure each AI coding tool to route through the Unbound Gateway.
All scripts must be run as root (or with administrator privileges). When deploying through your MDM provider, ensure the execution context is set to run with root-level permissions.
Before deploying, ensure your MDM provider is connected or devices are imported and you have an admin API key from gateway.getunbound.ai/connect.
In every command below, replace the following placeholders with your actual values:
  • YOUR_ADMIN_API_KEY — an admin API key from gateway.getunbound.ai/connect
  • https://backend.getunbound.ai — if your organization uses a custom backend URL, replace this with your own

​
Cursor

Run the following command to configure Cursor: 
python3 -c "$(curl -fsSL https://getunbound.ai/setup/cursor/mdm-install)" --backend-url https://backend.getunbound.ai --api-key YOUR_ADMIN_API_KEY

​
Claude Code

Claude Code supports two deployment methods depending on how your organization uses Anthropic.

​
Method 1: Using API Key

Use this method to route all Claude Code traffic through the Unbound Gateway without requiring an Anthropic subscription on the device: 
python3 -c "$(curl -fsSL https://getunbound.ai/setup/claude-code/gateway/mdm-install)" --backend-url https://backend.getunbound.ai --api-key YOUR_ADMIN_API_KEY

​
Method 2: With Anthropic Account

Use this method if the user already has an active Anthropic subscription. This configures hooks for tracking and analytics while preserving the existing Anthropic authentication: 
python3 -c "$(curl -fsSL https://getunbound.ai/setup/claude-code/hooks/mdm-install)" --backend-url https://backend.getunbound.ai --api-key YOUR_ADMIN_API_KEY

​
Gemini CLI

Run the following command to configure Gemini CLI: 
python3 -c "$(curl -fsSL https://getunbound.ai/setup/gemini-cli/gateway/mdm-install)" --backend-url https://backend.getunbound.ai --api-key YOUR_ADMIN_API_KEY

​
Codex

Codex supports two deployment methods depending on how your organization uses OpenAI.

​
Method 1: Using API Key

Use this method to route all Codex traffic through the Unbound Gateway without requiring an OpenAI subscription on the device: 
python3 -c "$(curl -fsSL https://getunbound.ai/setup/codex/gateway/mdm-install)" --backend-url https://backend.getunbound.ai --api-key YOUR_ADMIN_API_KEY

​
Method 2: With OpenAI Account

Use this method if the user already has an active OpenAI subscription. This configures hooks for tracking and analytics while preserving the existing OpenAI authentication: 
python3 -c "$(curl -fsSL https://getunbound.ai/setup/codex/hooks/mdm-install)" --backend-url https://backend.getunbound.ai --api-key YOUR_ADMIN_API_KEY

​
GitHub Copilot

Run the following command to configure GitHub Copilot. Hooks-based — works with both the VS Code extension and the copilot CLI on the user’s existing Copilot subscription: 
python3 -c "$(curl -fsSL https://getunbound.ai/setup/copilot/hooks/mdm-install)" --backend-url https://backend.getunbound.ai --api-key YOUR_ADMIN_API_KEY

​
Remove Unbound Configuration

To remove the Unbound Gateway configuration from a device, run that tool’s mdm-install command with only the --clear flag. Clearing does not require an API key or backend URL. This removes all Unbound-related settings for that tool and restores it to its default state. For example, to clear Cursor: 
python3 -c "$(curl -fsSL https://getunbound.ai/setup/cursor/mdm-install)" --clear

​
Keep enforcement in place

Deploying through MDM installs Unbound as managed settings that standard users can’t remove. Schedule the deployment to run daily so enforcement stays resilient.

Tamper Resistance

Best practices for keeping Unbound active on every device with managed settings.