{"version":"2.1.305","anchor":"skill-sync-scoped-settings-treated-as-set-when-sync-skills-o","canonical_anchor":"skill-sync-scoped-settings-treated-as-set-when-sync-skills-o","heading":"Skill sync settings now default to off when sync variables are set","tier":"notice","area":"Skills","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305\/e\/skill-sync-scoped-settings-treated-as-set-when-sync-skills-o","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305","markdown":"### Skill sync settings now default to off when sync variables are set\n\nWith `CLAUDE_CODE_SYNC_SKILLS` or `CLAUDE_CODE_SYNC_SESSION_REFS` set, a matching skill setting is now treated as off instead of left unset\n\n**Unclear.** It is not clear what feature reads this setting or what being off changes.\n\n**What**\n\nWhen `CLAUDE_CODE_SYNC_SKILLS` or `CLAUDE_CODE_SYNC_SESSION_REFS` is set, and a skill has a matching entry among its scoped settings, Claude Code now treats that setting as off when nothing else decides it. Before, it was left unset. These are environment variables, settings you put in your shell before starting Claude Code.\n\n**Why**\n\nThis changes the default for skill sync when either variable is on.\n\n- Area: Skills\n- Names: `CLAUDE_CODE_SYNC_SKILLS`, `CLAUDE_CODE_SYNC_SESSION_REFS`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: yes"}