{"version":"2.1.305","anchor":"new-ccr-early-sync-escape-hatch-after-a-settings-403","canonical_anchor":"new-ccr-early-sync-escape-hatch-after-a-settings-403","heading":"Cloud sessions can sync early even after a refused settings fetch","tier":"use","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305\/e\/new-ccr-early-sync-escape-hatch-after-a-settings-403","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305","markdown":"### Cloud sessions can sync early even after a refused settings fetch\n\nA new switch, `CLAUDE_CODE_CCR_EARLY_SYNC_AFTER_SETTINGS_REFUSAL`, lets cloud sessions take the early sync path when the settings fetch is refused\n\n**Unclear.** It is not clear whether this switch is set as an environment variable or by the server, or what its default is.\n\n**What**\n\nCloud 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`.\n\nWhen 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.\n\n**Why**\n\nA refused settings fetch no longer has to stop plugins and skills from syncing early in a cloud session when this switch is on.\n\n- Area: Cloud Sessions\n- Names: `CLAUDE_CODE_CCR_EARLY_SYNC_AFTER_SETTINGS_REFUSAL`, `CLAUDE_CODE_CCR_EARLY_PLUGINS_SYNC`, `CLAUDE_CODE_CCR_EARLY_SKILLS_SYNC`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}