Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.305entry #31

Claude Code v2.1.305 ·

Cloud sessions can sync early even after a refused settings fetch

A new switch, CLAUDE_CODE_CCR_EARLY_SYNC_AFTER_SETTINGS_REFUSAL, lets cloud sessions take the early sync path when the settings fetch is refused

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

Unclear It is not clear whether this switch is set as an environment variable or by the server, or what its default is.

What

Cloud sessions, which are Claude Code sessions run on remote machines, gain another early-sync switch beside CLAUDE_CODE_CCR_EARLY_PLUGINS_SYNC and CLAUDE_CODE_CCR_EARLY_SKILLS_SYNC: CLAUDE_CODE_CCR_EARLY_SYNC_AFTER_SETTINGS_REFUSAL.

When it is on and fetching settings fails with a 403 error (the server refusing access), Claude Code takes the early sync path instead of its usual one.

Why

A refused settings fetch no longer has to stop plugins and skills from syncing early in a cloud session when this switch is on.

Read from
Names in the bundleCLAUDE_CODE_CCR_EARLY_SYNC_AFTER_SETTINGS_REFUSALCLAUDE_CODE_CCR_EARLY_PLUGINS_SYNCCLAUDE_CODE_CCR_EARLY_SKILLS_SYNC
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 whether this switch is set as an environment variable or by the server, or what its default is.
The name it cites is new in this buildNew in this build: CLAUDE_CODE_CCR_EARLY_SYNC_AFTER_SETTINGS_REFUSAL

See this entry in the whole of v2.1.305 →

Feedback