Source Intelligence

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.

All of v2.1.228 Home All releases olderv2.1.227 v2.1.229newer
Claude Code v2.1.228

Slack ping origin plumbed through message handling, but nothing creates one

Not switched on
Useful2 Signal5
Messaging Notable

Messages can be tagged as coming from a Slack ping, but nothing in this build creates one.

A Slack-ping message origin is plumbed through display and queueing with no code path producing it.

What

A new message origin kind for Slack pings is wired through message display, prompt queueing, system-reminder wrapping and harness tag neutralisation, with its own equality check over channel, thread, message, Slack user, sender name and permalink. No code path in this build produces an origin of this kind.

Details
  • A Slack origin field is passed from the inbound bridge payload into the origin classifier, which currently ignores the argument
  • The classifier's two Slack observation checks are hard-coded to return false
Evidence

slack-ping

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

See this entry in the whole of v2.1.228 →