{"version":"2.1.265","anchor":"slack-tag-claude-tag-sessions-skip-syncing-remote-eval-f","canonical_anchor":"growthbook-experiment-targeting-gains-a-slacktagconnected-at","heading":"Feature-flag targeting now accounts for Slack-tag-connected accounts","tier":"internal","area":"Slack Integration","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/slack-tag-claude-tag-sessions-skip-syncing-remote-eval-f","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### Feature-flag targeting now accounts for Slack-tag-connected accounts\n\nFeature flag evaluation now knows whether an account has a Slack tag connected, and skips syncing flags to disk for those sessions\n\n**Unclear.** Why Slack-tag sessions specifically need to skip the feature-flag disk sync isn't explained by the finding.\n\n**What**\n\n- The remote-eval (Growthbook) client context used for feature-flag experiments now includes a `clientSlackTagConnected` attribute, derived from `slackTagConnected`, and the evaluation cache key now includes `slackTagConnected` alongside `id`\/`organizationUUID`.\n\n- Sessions where this attribute (also called \"Claude Tag\") is set now skip `syncRemoteEvalToDisk()` entirely, so remote eval feature flags aren't written to disk for those sessions.\n\n**Why**\n\nThis lets feature-flag experiments be targeted and cached separately based on whether an account has a Slack tag connected, and avoids persisting feature-flag state to disk for those sessions.\n\n- Area: Slack Integration\n- Names: `clientSlackTagConnected`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}