{"version":"2.1.287","anchor":"claude-code-ccr-skip-fresh-migrations-skips-startup-migratio","canonical_anchor":"claude-code-ccr-skip-fresh-migrations-skips-startup-migratio","heading":"New CLAUDE_CODE_CCR_SKIP_FRESH_MIGRATIONS skips setup steps for fresh cloud configs","tier":"use","area":"Cloud Sessions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/claude-code-ccr-skip-fresh-migrations-skips-startup-migratio","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### New `CLAUDE_CODE_CCR_SKIP_FRESH_MIGRATIONS` skips setup steps for fresh cloud configs\n\nSetting `CLAUDE_CODE_CCR_SKIP_FRESH_MIGRATIONS` lets a remote session with an untouched config skip Claude Code's startup migrations\n\n**Unclear.** It is not clear exactly what the remote-session condition checks.\n\n**What**\n\nWhen Claude Code starts, it runs migrations: steps that update your saved configuration to match newer versions. A new environment variable, `CLAUDE_CODE_CCR_SKIP_FRESH_MIGRATIONS`, lets it skip them. An environment variable is a named value you set outside Claude Code, for example in your shell. Claude Code skips the migrations only when all of these are true:\n\n- `CLAUDE_CODE_CCR_SKIP_FRESH_MIGRATIONS` is set.\n\n- Claude Code is running in a remote session.\n\n- The configuration has not been customised: no `autoUpdates` set to false, no model setting, and none of the other listed changes.\n\nIn that case Claude Code marks every migration as done and goes straight on without running any of them. Without the variable, every migration runs in order as before.\n\n**Why**\n\nThis is an opt-in way to start cloud sessions faster, since a fresh configuration has nothing for the migrations to update.\n\n- Area: Cloud Sessions\n- Names: `CLAUDE_CODE_CCR_SKIP_FRESH_MIGRATIONS`\n- Tier: Use it now\n- Useful: 5\/5\n- Signal: 3\/5"}