Skip to main content

Move Claude Code CLI users

If your developers use the Claude Code CLI, set it up separately from the desktop app. The desktop app takes its provider settings from its Claude Desktop on 3P configuration, not from ANTHROPIC_BASE_URL or settings.json, and passes them to the Code sessions it starts. The CLI reads environment variables, settings files, and Claude Code managed settings, which use a separate policy key.

This guide is for admins of organizations on Claude Enterprise plans.

This article is part of Move from Claude Enterprise to Claude Desktop on a cloud provider, which defines the terms wave, overlap period, and cutoff date.

The CLI and everything that runs locally work on every provider. After the move, developers sign in differently, your policies reach their computers differently, and some features aren't available.

Connect the CLI to your provider

Set the provider variables for Amazon Bedrock, Google Cloud, Microsoft Foundry, or an LLM gateway. Developers don't need a claude.ai browser login. With a gateway, set both the base URL and a gateway credential. With only the base URL, a saved claude.ai login stays the active credential, so its limits and billing still apply. Before a team rollout, pin your model versions.

Deliver policy to each device

Server-managed settings don't apply when a third-party provider or a custom base URL is set. Move those policies to managed settings on the device. You can deliver them as a managed-settings.json file, the com.anthropic.claudecode macOS profile, or the HKLM\SOFTWARE\Policies\ClaudeCode registry key. They take priority over user and project settings, apart from a few security-sensitive keys where a stricter value from a lower level still counts.

  • Limit which providers a computer can use: Set allowedProviders (Claude Code v2.1.285 or later). During the overlap period, a list such as ["anthropic", "bedrock"] lets developers use either one. After the move, list only the new provider. Keep "anthropic" on computers where users stay signed in to claude.ai in Claude Desktop, because their Cowork sessions are refused without it. For a gateway reached through ANTHROPIC_BASE_URL, list "customEndpoint" and put the gateway URL in the env block of the same managed source.

  • Remove old login settings: With gateway credentials, remove forceLoginMethod and forceLoginOrgUUID, because either key blocks gateway credentials at startup. On a cloud provider, those keys block a session only while certain credentials are still on the computer: ANTHROPIC_API_KEY, ANTHROPIC_AUTH_TOKEN, an apiKeyHelper credential, or an API key saved by an earlier Claude Console login.

Developers can run /status to see the active provider and where their settings come from. For telemetry, network hosts, and updates, see Data usage, Enterprise network configuration, and Advanced setup.

Track cost and usage

On Bedrock, Google Cloud, and Foundry, usage is billed per token to your cloud account, and cost controls are in your cloud billing console. Through a gateway, usage is billed per token to whoever owns the credential the gateway forwards. The claude.ai analytics dashboards and the Claude Code Analytics API don't cover this usage. For reporting by user, use OpenTelemetry or an LLM gateway.

What carries over for developers

Item

After the move

What to do

Settings, CLAUDE.md, auto memory, skills, subagents, commands, hooks, plugins, and MCP servers

Nothing, unless you log out (see below). Leave these folders in place during any cleanup.

Local session transcripts

They stay in ~/.claude/projects/ until cleanupPeriodDays removes them. The default is 30 days. claude --continue and claude --resume reopen them.

Test resuming a session in your pilot. On Bedrock, Google Cloud, and Foundry, the session's earlier model isn't restored. If a gateway's upstream rejects an earlier thinking signature, Claude Code drops the earlier thinking blocks and retries.

Cloud sessions

Anthropic stores them under the Claude account. --cloud isn't available when Claude Code is configured for a third-party provider, and --resume doesn't list cloud sessions.

Before the move, pull each session you need into the terminal with --teleport. It makes a local copy. It needs a claude.ai sign-in, a clean working tree, a checkout of the same repository, and the session's branch pushed to the remote.

Connectors from claude.ai

Not loaded when a third-party provider is active.

Add them as MCP servers at user or project scope, or deploy them through managed MCP configuration. Some Anthropic-hosted connectors, such as Microsoft 365, Gmail, and Google Calendar, don't support sign-in from a server you add yourself, so plan a different server for those.

Skills synced from claude.ai

Skill sync doesn't run in sessions on Bedrock, Google Cloud, or Foundry, or when a gateway credential replaces the claude.ai sign-in. Skills synced earlier stay on disk in ~/.claude/skills/synced/.

Copy any skill you rely on from ~/.claude/skills/synced/ into ~/.claude/skills/.

Plugins synced from claude.ai

Neither downloaded nor loaded in sessions on Bedrock, Google Cloud, or Foundry, because those sessions don't fetch feature flags from Anthropic. The same is true when ANTHROPIC_AUTH_TOKEN or apiKeyHelper supplies the credential.

Reinstall them from a marketplace, if one carries them.

Features that need a claude.ai sign-in

Not reachable from a provider. These include cloud sessions, Routines, managed Code Review, Ultrareview, Remote Control, the Chrome extension, and voice dictation. Channels and the analytics dashboard are also unavailable on Bedrock, Google Cloud, and Foundry. So are the Advisor and Code Mode. The CLI's web search is unavailable on Bedrock. Fast mode is unavailable on Bedrock and Foundry, and on Google Cloud it's limited to Claude Fable 5.2.

Use /loop for scheduling, GitHub Actions or GitLab CI/CD for cloud runs (GitHub Actions only on Foundry), and local /code-review. Decide whether developers still need Team or Enterprise seats.

What to watch for during the overlap period

Checklist for developers

Before the move

  • Update Claude Code to the version your admins specify.

  • Pull any cloud sessions you need into the terminal with claude --teleport. First make sure the session's branch is pushed to the remote, and clean your working tree.

  • List the claude.ai connectors you use, so they can be added as MCP servers.

  • Copy any skill you rely on out of ~/.claude/skills/synced/, and list the synced plugins you'll need to reinstall.

On the day you move

  1. Sign in to your cloud provider the way your admins describe, for example with aws sso login, gcloud auth application-default login, or az login.

  2. Start claude and run /status. Check the provider, the model, and the settings source.

  3. Reopen a recent session with claude --resume and confirm that it responds.

  4. Tell your admins about any tool or connector that's missing.

Did this answer your question?