Anthropic API / Anthropic API

Anthropic SDK copy() leaks inherited api_key — AccessTokenAuth silently disabled

Fix anthropic SDK client.copy() method that propagates parent api_key into child clients, preventing credential provider (OAuth, GCP, AWS) authentication from working Includes evidence for Anthropic API troubleshooting demand.

Source-backed Last updated May 23, 2026 1 source Needs local verification

Category: Anthropic API
Error signature: copy(credentials=...) carries over inherited api_key even when replacing with credentials provider; AccessTokenAuth short-circuits
Quick fix: Verify the account session, API key, provider settings, and environment where the failing tool is running.
Updated: May 23, 2026
Verification status: Source-backed
Evidence: 1 public source URL

Before you change production

This page includes public source URLs in the imported troubleshooting record. Compare those references with your version and environment before applying changes.

Reproduce the smallest failing action and save non-secret logs before changing configuration.
Check versions for Anthropic API, related SDKs, package managers, CI runners, and hosting providers.
Change one setting or dependency at a time, then rerun the same failing command or request.
Avoid destructive commands, credential rotation, billing changes, or security relaxations without a rollback plan.

What this error means

copy(credentials=...) carries over inherited api_key even when replacing with credentials provider; AccessTokenAuth short-circuits is a Anthropic API failure pattern reported for developers trying to fix anthropic sdk client.copy() method that propagates parent api_key into child clients, preventing credential provider (oauth, gcp, aws) authentication from working. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

PR #1557 on anthropics/anthropic-sdk-python (open, created 2026-05-17). Root cause: copy() always passes api_key=api_key or self.api_key into new client. When caller tries to replace a static key client with a credentials provider, the copied client still sends X-Api-Key so AccessTokenAuth short-circuits. Fix involves stopping propagation unless explicitly passed.

Common causes

PR #1557 on anthropics/anthropic-sdk-python (open, created 2026-05-17). Root cause: copy() always passes api_key=api_key or self.api_key into new client. When caller tries to replace a static key client with a credentials provider, the copied client still sends X-Api-Key so AccessTokenAuth short-circuits. Fix involves stopping propagation unless explicitly passed.

Quick fixes

Confirm the exact error signature matches copy(credentials=...) carries over inherited api_key even when replacing with credentials provider; AccessTokenAuth short-circuits.
Check the Anthropic API account, local tool state, and provider configuration involved in the failing workflow.
Verify the account session, API key, provider settings, and environment where the failing tool is running.

Platform/tool-specific checks

Verify the command, editor, extension, or API client that produced the error.
Compare local settings with CI, deployment, or editor-level settings when the error appears in only one environment.
Avoid deleting credentials, local model data, or project settings until the failing scope is clear.

Step-by-step troubleshooting

Capture the exact error message and the command, editor action, or request that triggered it.
Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
Review the source evidence below and compare it with your environment.
Apply one change at a time and rerun the smallest failing action.
Keep the working fix documented for the team or deployment environment.

How to prevent it

Keep provider/tool configuration documented.
Record non-secret diagnostics such as tool version, provider name, model name, and command path.
Add a lightweight check before CI or production workflows depend on the tool.

Diagnostic flow for this page

Match copy(credentials=...) carries over inherited api_key even when replacing with credentials provider; AccessTokenAuth short-circuits exactly before applying the quick fix.
Compare the failing environment with Anthropic API versions, account scope, provider settings, and deployment context.
Check the listed common causes in order, starting with the cause that best matches your logs.
Use the evidence status below to decide whether to confirm against public sources or official documentation.
Apply one reversible change, rerun the smallest failing action, and keep rollback notes.

FAQ

What does copy(credentials=...) carries over inherited api_key even when replacing with credentials provider; AccessTokenAuth short-circuits mean in Anthropic API?

copy(credentials=...) carries over inherited api_key even when replacing with credentials provider; AccessTokenAuth short-circuits indicates the workflow described by "Anthropic SDK copy() leaks inherited api_key — AccessTokenAuth silently disabled" failed in a Anthropic API context. Start by confirming the exact signature and the component that emitted it.

What should I check first for copy(credentials=...) carries over inherited api_key even when replacing with credentials provider; AccessTokenAuth short-circuits?

Check whether this cause matches your environment: PR #1557 on anthropics/anthropic-sdk-python (open, created 2026-05-17). Root cause: copy() always passes api_key=api_key or self.api_key into new client. When caller tries to replace a static key client with a credentials provider, the copied client still sends X-Api-Key so AccessTokenAuth short-circuits. Fix involves stopping propagation unless explicitly passed.

Is the copy(credentials=...) carries over inherited api_key even when replacing with credentials provider; AccessTokenAuth short-circuits guidance source-backed?

The "Anthropic SDK copy() leaks inherited api_key — AccessTokenAuth silently disabled" page is labeled source-backed. It has 1 public source URL from github.com, so use that evidence status when deciding how much additional verification you need.

When should I avoid the quick fix for copy(credentials=...) carries over inherited api_key even when replacing with credentials provider; AccessTokenAuth short-circuits?

For "Anthropic SDK copy() leaks inherited api_key — AccessTokenAuth silently disabled", avoid applying "Verify the account session, API key, provider settings, and environment where the failing tool is running." when the error text differs, the affected version or provider is different, or the change would touch credentials, billing, DNS, production deploy settings, or irreversible data.

What should I collect before debugging copy(credentials=...) carries over inherited api_key even when replacing with credentials provider; AccessTokenAuth short-circuits?

For "Anthropic SDK copy() leaks inherited api_key — AccessTokenAuth silently disabled", collect the failing Anthropic API command or request, non-secret configuration, versions, timestamps, request IDs when available, and the smallest reproduction that still triggers the signature.