{"version":"2.1.319","anchor":"share-and-feedback-bundle-fallback-reworked","canonical_anchor":"share-and-feedback-bundle-fallback-reworked","heading":"\/share may send a session bundle without the environment variable","tier":"notice","area":"Sharing","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/share-and-feedback-bundle-fallback-reworked","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### \/share may send a session bundle without the environment variable\n\n`\/share` can now produce a session bundle when feedback is turned off, or when a share switch is set, not only with `CLAUDE_CODE_ENABLE_SHARE_BUNDLE`\n\n**Unclear.** Whether `\/share` now sends a bundle by default, without the environment variable or a setting.\n\n**What**\n\nA bundle here is the package `\/share` sends, which can include the whole session transcript. Before, `\/share` built one only when `CLAUDE_CODE_ENABLE_SHARE_BUNDLE` or a setting was set. That check is no longer made directly at this point. Instead:\n\n- Feedback turned off: `\/share` can still produce a bundle.\n\n- Otherwise: a share switch can make any share command produce a bundle.\n\n**Why**\n\nThis could make `\/share` send a bundle for more people than before, so it is worth checking what a share sends if your session holds sensitive material.\n\n- Area: Sharing\n- Names: `\/share`, `CLAUDE_CODE_ENABLE_SHARE_BUNDLE`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: yes"}