You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
Cloud SyncArea: what it touches
ImprovementsKind: in v2.1.281,
ImprovementsSection of the release
What
When 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:
the environment Claude Code was started in
your own settings, for example ~/.claude/settings.json
It 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.
Why
A 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.
One source agreesOne thing we can check says the same as this entry.
Anthropic's release notes agreeAdded "attribution": false in settings.json to hide all commit and PR attribution; older CLI versions skip a settings file that holds it, so…
