Follow Discord
Sweep 29 Sep 2026 · 18:10Z Build v2.1.285 506 read Stable v2.1.280 Latest v2.1.285 Next v2.1.285 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.285 ·

Claude Code remembers which models your AWS or Google Cloud account can use

Model access checks for AWS and Google Cloud accounts are now saved and reused at start-up, unless CLAUDE_CODE_SKIP_MODEL_ACCESS_MEMORY is set

You'll notice Improvements
JSON All of v2.1.285
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
ModelsArea: what it touches
ImprovementsKind: in v2.1.285,
ImprovementsSection of the release
What

When you use Claude through AWS or Google Cloud credentials, Claude Code checks at start-up which models your account can use. It now saves each result, allowed or refused, per account in a cache/model-access.json file and can reuse it on later starts.

To tell accounts apart, Claude Code builds a fingerprint of your AWS config and credentials files or your gcloud identity files. If one of those files is over 4 MB or is not a regular file, saved results are not reused.

To turn this memory off, set CLAUDE_CODE_SKIP_MODEL_ACCESS_MEMORY. Related log lines start with [3p-model-memory].

Why

Start-up can skip some model checks, so it may be quicker. A saved answer can go out of date, though: if your model access changes and Claude Code still behaves as before, set CLAUDE_CODE_SKIP_MODEL_ACCESS_MEMORY.

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 not clear how long saved results are kept or exactly which providers are covered.

See this entry in the whole of v2.1.285 →

Feedback