{"version":"2.1.281","anchor":"claude-code-legacy-bundle-is-ignored-when-a-project-settings","canonical_anchor":"claude-code-legacy-bundle-is-ignored-when-a-project-settings","heading":"CLAUDE_CODE_LEGACY_BUNDLE is ignored when a project settings file sets it","tier":"notice","area":"Cloud Sync","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/claude-code-legacy-bundle-is-ignored-when-a-project-settings","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### CLAUDE_CODE_LEGACY_BUNDLE is ignored when a project settings file sets it\n\nCLAUDE_CODE_LEGACY_BUNDLE is ignored with a warning when it comes from a settings file rather than your launch environment or own settings\n\n**What**\n\nWhen Claude Code uploads your repository to a cloud session, it packs it into a git bundle, a single file holding the repository. The environment variable `CLAUDE_CODE_LEGACY_BUNDLE` switches that packing back to the older, less hardened method. It now only counts when it comes from:\n\n- the environment Claude Code was started in\n\n- your own settings, for example `~\/.claude\/settings.json`\n\nIt is ignored, with a warning, when another settings file sets it or when a settings layer moves `HOME` or `CLAUDE_CONFIG_DIR`. In those cases the hardened method runs, and telemetry records `legacy_switch_ignored`.\n\n**Why**\n\nA project's settings file cannot quietly turn off the hardened upload for you. If you rely on the legacy method, set the variable in your shell or your own user settings.\n\n- Area: Cloud Sync\n- Names: `CLAUDE_CODE_LEGACY_BUNDLE`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}