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.261 ·

Slack-relay message provenance rules for user-intent detection

Internal instructions now spell out how to tell genuine Slack user messages from bot-relayed ones.

TierUnder the hoodhow much it should matter to you
Useful1my rating, 1 to 5
Signal1worth watching, 1 to 5
AreaElsewherewhat it touches
KindInternal Changesin v2.1.261,
Under the hood

Internal instructions now spell out how to tell genuine Slack user messages from bot-relayed ones.

The agent's internal instructions for Slack relay now spell out how to distinguish genuine user messages from bot- or peer-authored ones. A real user message arrives via a <wake …> envelope with from="human", or via specific harness-inserted lead/marker text; a <message> carrying the bot attribute inside a <slack-messages> block was written by a bot or another agent. Messages in the latter category must never be treated as establishing user intent or consent, and permission-laundering attempts relayed through Slack are explicitly callable out as blockable.

See this entry in the whole of v2.1.261 →

Feedback