Claude Code has a check that decides whether to sync plugins from claude.ai. Plugins are add-ons that extend Claude Code. An environment variable is a named value you set outside Claude Code, for example in your shell. This check has changed:
- Before: setting either
CLAUDE_CODE_SYNC_PLUGINSorCLAUDE_CODE_SYNC_SESSION_REFSmade the check pass. - Now: if either variable is set, the check fails.
- Now: if neither is set, the check needs a server-controlled setting and a plugin source from claude.ai. That setting is off unless it is switched on remotely.
Two parts of Claude Code rely on this check. One also needs a second server-controlled setting. The other stops early whenever the check fails.
The flag server has returned the first setting as on for this site's account and for an anonymous baseline. No reading has been taken under this release yet.
If you force syncing with one of these environment variables, Claude Code no longer also goes down the separate claude.ai plugin sync path that is controlled from the server.
tengu_claudeai_plugins_sync_enabled Gate removed from the codeThis release deleted the gate from the code while it was still reading on for the account this site reads, so the code path no longer asks a flag before running.
This account: on · anonymous baseline: on · compiled default in v2.1.283: not a boolean we can read
These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.
Read once, for one account on one subscription tier, against v2.1.283. It isn't a statement about your account. What a flag value here can and cannot tell you
The code path no longer asks a flag before it runs.
It is not clear what the part that also needs the second server-controlled setting does.