Skip to main content
The Claude Code CLI and everything that runs locally work on every provider. For setup instructions per provider, see the Enterprise deployment overview. To skip straight to what is missing on your provider, see the summary by provider tabs. In the tables below, ✓ means available, ✗ means not available, and “See note” links to a footnote for partial support. A qualifier after ✓ narrows availability to that subset, and “Admin-enabled” means the feature is off until an organization admin turns it on.

​
Availability by model provider

How you authenticate determines which features Claude Code can reach. For a single list of what is missing on your provider, see the summary by provider tabs. To find your column in the tables:
  • Claude subscription: you sign in with a claude.ai account on the Pro, Max, Team, or Enterprise plan
  • Anthropic Console: you authenticate with an Anthropic API key
  • Amazon Bedrock: you use Claude models from the Amazon Bedrock model catalog and set CLAUDE_CODE_USE_BEDROCK. The Mantle endpoint (CLAUDE_CODE_USE_MANTLE) is covered by this column
  • Claude Platform on AWS: you bought Claude through AWS Marketplace but call the Anthropic API, and set CLAUDE_CODE_USE_ANTHROPIC_AWS
  • Google Cloud’s Agent Platform: Google-operated; you set CLAUDE_CODE_USE_VERTEX
  • Microsoft Foundry: Anthropic-operated; you set CLAUDE_CODE_USE_FOUNDRY

​
Features available on every provider

These work on every provider: Three of these have provider-specific differences:
  • MCP servers: connectors from claude.ai load only when your claude.ai subscription is the active authentication method. Tool search is off by default when ANTHROPIC_BASE_URL points to a non-first-party host, and isn’t supported on Google Cloud’s Agent Platform models earlier than the Claude 4.5 generation or on Microsoft Foundry deployments hosted on Azure
  • Subagents: the built-in Explore subagent caps its inherited model at Opus on the Claude API, and inherits the main conversation’s model directly on any other provider, including Claude Platform on AWS
  • Commands: /design-sync, /import with its claude import subcommand form, and /radio are unavailable on Amazon Bedrock, Google Cloud’s Agent Platform, Microsoft Foundry, and Claude Platform on AWS, /voice requires a claude.ai account, and /list-agents and its alias /peers are available only in sessions where cross-session messaging is enabled

​
Features that require a Claude subscription

These require signing in with a claude.ai account and are not reachable with an Anthropic Console API key or from a third-party provider: Desktop is the partial exception: gateway routing can be configured in the app or by an administrator, Enterprise deployments can route Desktop to Google Cloud’s Agent Platform or a gateway provider via managed settings, and Claude Desktop on 3P runs the Code tab on Amazon Bedrock, Google Cloud’s Agent Platform, Microsoft Foundry, or a self-hosted LLM gateway. For per-plan availability of these features, see Availability by subscription plan.

​
CLI capabilities that vary by provider

These features work in the local CLI but depend on a server-side capability that not every provider exposes.
FeatureClaude subscriptionAnthropic ConsoleAmazon BedrockClaude Platform on AWSGoogle Cloud’s Agent PlatformMicrosoft Foundry
Web search✓✓✗✓See note 1✓ (deployments hosted on Anthropic)
Fast mode✓ (Owner-enabled on Team and Enterprise)✓ (provisioned organizations)✗✗✗✗
Auto mode✓✓See note 2✓See note 2See note 2
Advisor✓✓✗✗✗✗
Cross-session messaging✓ (macOS and Linux) 6✓ (macOS and Linux) 6✗✗✗✗
Channels✓✓✗✗✗✗