Centrally configure AI inference providers for your organization so developers don’t need individual API keys.
Cline Enterprise lets administrators configure inference providers once from the Cline admin console. All organization members automatically receive the provider settings when they sign in — no individual API key distribution required.
The admin selects a provider, enters credentials and settings, and saves the configuration in the Cline admin console.
Automatic distribution
Configuration is pushed to all signed-in organization members automatically. Members cannot switch to other providers or their personal Cline accounts.
Simplified member onboarding
New members get access to the configured provider immediately after signing in with SSO — no setup required on their part.
Consistent experience
Every developer in the organization uses the same models, regions, and settings.
Once remote provider configuration is enabled and saved, organization members cannot switch to personal Cline accounts or select other providers. Ensure the configured provider is accessible to all members before saving.
In Settings → Cline Settings, open the API Provider dropdown and select Amazon Bedrock.
2
Configure Bedrock settings
Region (required)
Enter your AWS region, for example us-east-1 or us-west-2. This region is enforced for all organization members.
us-east-1 and us-west-2 have the broadest model availability. Check the AWS Global Infrastructure page if you need a specific region.
Custom VPC endpoint (optional)
If your organization uses a private VPC endpoint for Bedrock, specify it here to route all API calls through your network perimeter.See AWS PrivateLink for Bedrock for setup instructions.
Cross-region inference (optional)
Enable this to allow Bedrock to automatically route requests to other regions when your primary region has capacity constraints. Useful for maintaining availability during high-demand periods.See Inference Profiles for details.
Global inference profile (optional)
Routes requests to the optimal AWS region globally based on availability and latency.
Prompt caching (optional)
Caches consistent portions of prompts across requests, reducing latency and cost for repeated interactions.See Prompt caching in Bedrock.
3
Save the configuration
Close the provider configuration panel and click Save on the settings page. All signed-in organization members begin using Amazon Bedrock with your settings immediately.
Click Save on the main settings page — closing the configuration panel alone does not save.
A running LiteLLM proxy instance accessible from your team’s development environments
The base URL of your LiteLLM proxy
Optionally, a master key if your proxy requires authentication
If you have not deployed a LiteLLM proxy yet, work with your infrastructure team to stand one up first. See the LiteLLM documentation for deployment options.
In Settings → Cline Settings, open the API Provider dropdown and select LiteLLM.
2
Configure LiteLLM settings
Base URL (required)
Enter the full URL of your LiteLLM proxy, for example https://litellm.yourcompany.com or http://your-proxy:4000.
Use HTTPS in production. Verify the URL is reachable from all developer machines and CI environments that will use Cline.
Master key (optional)
If your LiteLLM proxy requires authentication, enter the master key here. This key is used to authenticate all requests from organization members — members do not need to manage individual keys.
The master key grants full access to your LiteLLM proxy. Store it securely and rotate it according to your organization’s key management policies.
3
Save the configuration
Close the provider configuration panel and click Save on the settings page. Organization members receive the LiteLLM configuration automatically.
Click Save on the main settings page — closing the configuration panel alone does not save.
If a master key is configured at the organization level, members need no additional credentials — access is fully managed. If no master key is configured, members add their individual LiteLLM API key in the Cline VS Code extension.
You can change provider settings at any time from Settings → Cline Settings. Changes take effect for all organization members immediately after you save.To switch to a different provider entirely, select the new provider from the API Provider dropdown, complete the configuration, and save. Notify your team that they may need to configure new credentials locally.