Source Intelligence
Follow Discord
Sweep 28 Aug 2026 · 00:00Z Build v2.1.250 478 read Stable v2.1.236 Latest v2.1.250 Next v2.1.251 Feeds RSS JSON llms.txt
Reading a new release v2.1.251 Analysing changes · 2/5 Deeper second pass · 0/5 agents 427 findings $12.75 so far

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

One change

Good habits for working with Claude Tag

claude-tag/users/good-habits

first seen The page's own history The capture it came from

Nearest release: v2.1.248, published 3 hours after this site recorded the change. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.

claude-tag/users/good-habits Changed · +1 / -1 lines

from line 138
 
 A private channel is readable only from inside it. Inviting Claude lets it work in that channel, but Claude can't read the private channel's messages from any other channel or DM. To ask about a private channel, ask in that channel.
 
-Channels in a different workspace stay out of reach. In a Slack Connect channel, one shared with another company, Claude works only where your admin's guest setting allows it, and then with channel-only access; see [Slack Connect channels](/docs/claude-tag/admins/restrict-access#externally-shared-channels).
+Channels in a different workspace and Slack Connect channels stay out of reach.
 
 When more than one surface would work, prefer a channel. Work that happens there compounds, because Claude can draw on it in later threads and teammates can find it, redirect it, or build on it.