Follow Discord
Sweep 01 Oct 2026 · 17:27Z Build v2.1.287 508 read Stable v2.1.285 Latest v2.1.287 Next v2.1.287 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.286entry #14

Claude Code v2.1.286 ·

AWS and Google Cloud credential refresh commands run one at a time across sessions

awsAuthRefresh and gcpAuthRefresh now run in one Claude Code process at a time, report clearer outcomes, and respect Stop

Group of 4 Use it now Notable New Features
JSON All of v2.1.286
Use it nowTier: how much it should matter to you
4Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
AuthArea: what it touches
New FeaturesKind: in v2.1.286,
What probably matters to youSection of the release

What

awsAuthRefresh and gcpAuthRefresh are settings that name your own command for renewing Amazon Bedrock or Google Cloud credentials. The way Claude Code runs these commands was rewritten.

  • Only one Claude Code process runs a given refresh command at a time. Other processes wait and show "Another Claude Code process is running your ... command", telling you to finish signing in where that session started it, or to stop the request and send it again to sign in there instead.
  • A waiting process can ask the one running the command to hand over the sign-in, and it can detect when that process has gone away. The lock and related files are kept under .gcp_auth_refresh and .aws_auth_refresh.
  • The refresh now ends as 'ok', 'failed' or 'interrupted' instead of simply succeeded or failed. Cancelling closes the sign-in status display, and a command stopped by a signal counts as interrupted with no error printed.
  • Pressing Stop is now noted by any refresh that is waiting.
  • When the environment variable CLAUDE_CODE_CONFIG_PROBE is set, both refreshes are skipped without running your command. It is removed from the environment passed to child processes. Nothing in Claude Code sets it, so a host program such as an IDE would have to.

Before, each process kept one refresh at a time with a rate limit, with no shared lock and no handling for Stop.

Why

If you run several Claude Code sessions, they no longer each open a browser sign-in for the same refresh command. Cancelling a sign-in produces fewer misleading errors.

Read from
Names in the bundleCLAUDE_CODE_CONFIG_PROBEawsAuthRefreshgcpAuthRefresh
Since it was published

The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.

Added since A small documentation edit on Claude Code on Claude Platform on AWS touched a line naming awsAuthRefresh after this was published. If your SSO credentials expire mid-session, configure [`awsAuthRefresh`](/docs/en/amazon-bedrock#advanced-credential-configuration) so Claude Code re-runs your login command and retries instead of failing. Add the command to your [settings… claude-platform-on-aws see the edit
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtIt is unclear which program sets this variable and what the configuration check it describes does.
Anthropic's documentation agreesA small documentation edit on Claude Code on Claude Platform on AWS touched a line naming awsAuthRefresh after this was published.
The name it cites is new in this buildNew in this build: CLAUDE_CODE_CONFIG_PROBE

See this entry in the whole of v2.1.286 →

Feedback