Follow Discord
Sweep 22 Sep 2026 · 17:19Z Build v2.1.280 501 read Stable v2.1.267 Latest v2.1.280 Next v2.1.280 Feeds RSS JSON llms.txt Unofficial
Claude Code v2.1.265 ·

Feature-flag targeting now accounts for Slack-tag-connected accounts

← All of v2.1.265 Home All releases

Feature flag evaluation now knows whether an account has a Slack tag connected, and skips syncing flags to disk for those sessions

TierUnder the hoodhow much it should matter to you
Useful1my rating, 1 to 5
Signal1worth watching, 1 to 5
AreaSlack Integrationwhat it touches
KindInternal Changesin v2.1.265,
Group of 2 Under the hood No documentation found

Feature flag evaluation now knows whether an account has a Slack tag connected, and skips syncing flags to disk for those sessions

What

  • 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.
  • 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.

Why

This 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.

Read from
Names in the bundleclientSlackTagConnected
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtWhy Slack-tag sessions specifically need to skip the feature-flag disk sync isn't explained by the finding.

See this entry in the whole of v2.1.265 →

Feedback