{"version":"2.1.302","anchor":"claude-code-sync-skills-gate-in-a-hosted-worker-check","canonical_anchor":"claude-code-sync-skills-gate-in-a-hosted-worker-check","heading":"CLAUDE_CODE_SYNC_SKILLS now counts in a check that only runs in hosted worker sessions","tier":"internal","area":"Skills","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302\/e\/claude-code-sync-skills-gate-in-a-hosted-worker-check","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302","markdown":"### CLAUDE_CODE_SYNC_SKILLS now counts in a check that only runs in hosted worker sessions\n\nA new check that applies only in hosted worker sessions can be satisfied by setting the CLAUDE_CODE_SYNC_SKILLS environment variable\n\n**Unclear.** It is not clear what this check turns on or off, or what its other conditions are.\n\n**What**\n\nClaude Code has a new check that always answers no unless the session is running as a hosted worker, meaning a session run on a remote machine rather than on your own computer. Inside a hosted worker session, the check looks at several conditions. Setting the environment variable `CLAUDE_CODE_SYNC_SKILLS` satisfies one of them. An environment variable is a named value you set in your shell before starting Claude Code.\n\n`CLAUDE_CODE_SYNC_SKILLS` already existed. This is one more place where Claude Code reads it.\n\n**Why**\n\nSyncing skills in hosted worker sessions looks like something `CLAUDE_CODE_SYNC_SKILLS` can now help control. Skills are packaged instructions Claude can load for a task.\n\n- Area: Skills\n- Names: `CLAUDE_CODE_SYNC_SKILLS`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}