Enterprise Provider Configuration
Configure inference providers through the Cline hosted admin console for centralized organization management
Remote Provider Configuration allows administrators to centrally configure inference providers for their entire organization through the Cline hosted admin console. This approach ensures consistent provider access, security policies, and cost management across all team members without requiring individual developer setup or infrastructure deployment.
How Remote Configuration Works
Remote configuration operates through Cline's hosted service at app.cline.bot, where administrators can:
Centralized Setup
Configure providers once for the entire organization through the web-based admin console.
Automatic Enforcement
Team members automatically receive the configured provider settings when signed into their organization.
Simplified Onboarding
New team members get instant access to inference providers without complex individual configuration.
Consistent Experience
Ensure all team members use the same models, regions, and settings organization-wide.
Which products support each control
Cline products read the organization's remote configuration when a member signs in to the organization. Each product supports only the controls marked Yes below. Members who use Cline Desktop or the CLI can choose other providers and MCP servers.
| Control | VS Code and JetBrains | CLI | Cline Desktop |
|---|---|---|---|
| Rules and workflows | Yes | Yes | No |
| Skills | Yes | No | No |
| Allowed providers and provider settings | Yes | No | No |
| Members can't switch organization or use a personal account | Yes | No | No |
| Enable MCP Marketplace (when off, also blocks local MCP servers) | Yes | No | No |
| Allow members to use their own servers (MCP) | Yes | No | No |
| Organization MCP servers | Yes | No | No |
| Cline Telemetry | Yes | No | No |
| Allow YOLO mode | No | No | No |
| Allow Kanban | No | No | No |
The VS Code and JetBrains extensions show a lock icon on settings that the organization controls. Admins and Owners can choose Opt out of remote config on the Account page to work without the organization's settings; members can't.
To choose which products to recommend, check which controls your organization relies on. For example, if members must use only your approved providers, deploy the VS Code or JetBrains extension.
Files Cline writes to the workspace
To apply the organization's rules and workflows, Cline writes them, and a copy of the organization's settings, into the folder it's working in: .cline/enterprise/ in the CLI, and .cline/remote-config/ in the VS Code and JetBrains extensions. Cline rewrites these files when the organization's settings change. The copy of the settings can include the access keys for prompt storage, so add these patterns to your repository's .gitignore. The **/ prefix also matches the folders below the repository root, for example when someone opens a subfolder in VS Code:
**/.cline/enterprise/
**/.cline/remote-config/Supported Providers
Cline supports remote configuration for the following inference providers:
| Provider | Use Case | Configuration | Member Setup |
|---|---|---|---|
| Cline | Organizations using Cline's native provider with centralized API key management | API provider selection, model access | No individual API keys needed — fully managed by organization |
| Amazon Bedrock | Organizations using AWS infrastructure | Region selection, VPC endpoints, cross-region inference, global inference, prompt caching | AWS credential configuration (API key, CLI profile, or credential chain) |
| Google Vertex AI | Organizations using Google Cloud Platform | Project ID, region selection, model access | Google Cloud credential configuration (service account, SDK, or ADC) |
| Azure Foundry | Organizations using Azure OpenAI or Azure AI services | Base URL, Azure API version, Azure identity authentication, custom headers | API key configuration in the extension |
| Anthropic | Organizations using the Anthropic API directly | Optional custom base URL for proxy deployments, model access | API key configuration in the extension |
| OpenAI Compatible | Organizations using any OpenAI-compatible endpoint (self-hosted, vLLM, custom proxies) | Base URL, custom headers, model access | API key configuration in the extension |
| LiteLLM | Organizations requiring multi-model access through a unified proxy | Proxy endpoint, authentication, model routing | API key or endpoint configuration (or centralized with Master Key) |
Azure Foundry uses the OpenAI Compatible provider configuration with Azure-specific settings (API version, Azure identity authentication). See the OpenAI Compatible admin configuration for setup instructions.
Configuration Process
The typical remote configuration process follows these steps:
Administrator Setup
Access the Cline admin console and configure the desired inference provider with organization-wide settings.
Automatic Distribution
Provider configuration is automatically distributed to all organization members signed into Cline.
Member Credential Setup
Team members add their individual credentials (API keys, AWS profiles, etc.) to connect to the configured provider. For some providers like Cline and LiteLLM (with Master Key), no individual credentials are needed.
Immediate Access
Once credentials are configured, members can immediately start using the inference provider through Cline.
Benefits of Remote Configuration
For Administrators
- Centralized Control: Manage all provider settings from one location
- Security Compliance: Ensure consistent security policies across the organization
- Easy Updates: Change provider settings organization-wide instantly
For Team Members
- Simplified Setup: No need to research provider configuration options
- Consistent Experience: Same models and features available to everyone
- Quick Onboarding: Get started immediately with pre-configured providers
- Focus on Development: Spend time coding instead of configuring inference providers
Getting Started
To get started with provider remote configuration:
- Choose Your Provider: Select the inference provider that best fits your organization's needs and existing infrastructure
- Admin Configuration: Follow the provider-specific admin configuration guide
- Member Onboarding: Have team members complete the provider-specific member configuration
- Start Developing: Begin using Cline with centrally managed inference provider access
Select your provider below to begin the configuration process:
-
Amazon Bedrock：AWS-based AI models with enterprise security and compliance features.
-
Google Vertex AI：Google Cloud's AI platform with Gemini models and regional control.
-
OpenAI Compatible：Any OpenAI-compatible endpoint, including Azure Foundry.
-
Anthropic：Direct Anthropic API access with optional custom base URL configuration.
-
LiteLLM：Unified proxy for accessing 100+ AI models through a single interface.