Follow Discord
Sweep 10 Nov 2026 · 02:18Z Build v2.1.322 539 read Stable v2.1.311 Latest v2.1.322 Next v2.1.322 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.265entry #221

Claude Code v2.1.265 ·

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

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

Group of 2 Under the hood No documentation found Internal Changes
JSON All of v2.1.265
Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
Slack IntegrationArea: what it touches
Internal ChangesKind: in v2.1.265,
Internal ChangesSection of the release

Unclear Why Slack-tag sessions specifically need to skip the feature-flag disk sync isn't explained by the finding.

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