awsAuthRefresh
A Claude Code settings key, read out of the shipped bundle. It was in the build from v2.1.138 and was gone by v2.1.284.
Refresh expired Bedrock credentials in .aws with your own command
Anthropic's own wording. Read off All settings, captured 2026-10-22.
In the changelogs
20Releases whose published page names awsAuthRefresh.
-
v2.1.304
Credential helper commands no longer run in some kinds of Claude Code process
apiKeyHelper, awsAuthRefresh and three other helper settings are skipped in processes pinned to the stored login and in tool-server daemons
found in this entry's text
-
v2.1.304
otelHeadersHelper and awsAuthRefresh now match project settings in one more case
The check that ties an otelHeadersHelper or awsAuthRefresh command to project settings now passes in one more case
found in this entry's text, named in this entry
-
v2.1.300
AWS sign-in refresh command can now be skipped in some situations
Claude Code now skips your AWS auth refresh command in certain situations, reports it as failed and logs a reason
found in this entry's text, named in this entry
-
v2.1.286
New CLAUDE_CODE_CONFIG_PROBE variable stops cloud credential refresh commands
With CLAUDE_CODE_CONFIG_PROBE set, Claude Code skips the awsAuthRefresh and gcpAuthRefresh commands instead of running them
found in this entry's text, named in this entry
-
v2.1.286
Cancelling an AWS or Google Cloud credential refresh no longer shows an error
Credential refresh commands now end as succeeded, failed or interrupted, and an interrupted one closes quietly without printing an error
found in this entry's text, named in this entry
-
v2.1.286
Only one Claude Code window at a time runs your cloud sign-in refresh command
When several Claude Code processes need
gcpAuthRefreshorawsAuthRefreshat once, only one runs it and the others wait or take overfound in this entry's text, named in this entry
-
v2.1.286
AWS and Google Cloud credential refresh runs once at a time and respects Stop
Credential refresh commands set in
awsAuthRefreshandgcpAuthRefreshare now shared by everyone waiting, and stopping is noted by the waitfound in this entry's text, named in this entry
-
v2.1.284
Bedrock model access check is redone when you switch AWS credentials
Claude Code's saved check that a Bedrock model is reachable is now tied to your AWS profile, keys, role and credential settings
found in this entry's text
-
v2.1.281
Settings merge gains a credential-helper filter that is inert in this build
A filter that could strip credential helper settings from settings files is built in but does nothing yet
found in this entry's text
-
v2.1.281
AWS/GCP auth refresh commands run under a new process supervisor that kills the whole process tree on timeout, abort or shutdown
awsAuthRefresh and gcpAuthRefresh commands now stop together with everything they started on timeout, cancel or shutdown
found in this entry's text, named in this entry
-
v2.1.248
Memory API endpoint and token environment variables
Two environment variables can point Claude Code at a memory service with a token.
found in this entry's text
-
v2.1.247
AWS auth refresh accepts a structured command
awsAuthRefresh now accepts a structured file, args and env form so no shell is involved.
named in this entry, found in this entry's text
-
v2.1.223
Policy-settings environment stripping is case-insensitive
Environment variables your org policy blocks can no longer sneak through by changing their capitalization.
found in this entry's text
-
v2.1.186
AWS Credential Refresh in Login Wizard
found in this entry's text
-
v2.1.167
Auth-helper settings filtered under explicit host management
found in this entry's text
-
v2.1.72
GCP Auth Refresh
found in this entry's text
-
v2.0.24
Automatic AWS Credential Initialization for Bedrock
found in this entry's text
-
v2.0.2
AWS Credential Workspace Trust Checks
found in this entry's text
-
v1.0.53
New Features
found in this entry's text
-
v1.0.53
Configuration
found in this entry's text
First cited
2The earliest release whose published evidence quoted awsAuthRefresh was v2.1.286, 30 Sep 2026. That is the oldest release this project wrote about it, so it is a floor on the name's age and not the release that introduced it. It is not a presence reading: which builds carried the name is the table below.
Presence across releases
2Build by build
150One row per release since the first build this name was read out of. Absent means the build was read and the name was not in it, never mined means no bundle for that release was ever archived, and a declared type or a default is only ever what that release's own bundle stated.
Read out of the published npm bundle release by release, and out of Anthropic's own documentation as this site captured it. Nothing on this page is a description anybody here wrote about what the settings key does. All settings keys.