Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.247 Home All releases ←olderv2.1.246 v2.1.248newer→
Claude Code v2.1.247

AWS auth refresh accepts a structured command

Use it now
Useful3 Signal2
Auth Notable

awsAuthRefresh now accepts a structured file, args and env form so no shell is involved.

awsAuthRefresh
What

The awsAuthRefresh setting, which runs a command to refresh AWS credentials, now takes either the old shell string or a structured {file, args, env} form that avoids a shell.

Details
  • For the structured form the executable is resolved and rejected unless it sits in a safe directory: "AWS auth refresh: executable not found in a safe directory".
  • .cmd and .bat targets are quoted and run through a shell.
  • Failure and timeout messages now name the command that was run instead of pointing at the settings key.
Evidence

AWS auth refresh: executable not found in a safe directory

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.247 →