Slack turns from a server-verified human get a marker so Claude treats them as you without extra confirmation.
What's wrong with this entry?
Turns relayed from a bound Slack thread whose sender the server verified as human are now prefixed with a fixed marker, and a new prompt paragraph tells the model that a turn opening with exactly that marker is its own user and does not need extra confirmation, while bot-attributed messages inside a Slack message block never establish user intent. Both are emitted only when CLAUDE_CODE_ENTRYPOINT is claude_in_slack or claude-in-slack; otherwise the paragraph is empty.
- The paragraph replaces the previous cross-session messages rule in the prompt.
- The escaping helper for non-verified relayed text now also engages for Teams (
claude-in-teams) and for a third surface whose check unconditionally returns false, a placeholder with no way to be enabled in this build.
[Verified human message relayed from the bound Slack thread]:
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
Slack tagging wiring in the environment, status line and tool refresh
Both mention slack integration
-
v2.1.234
Groundwork for a Slack tagging integration, present but inert
Both mention slack integration
-
v2.1.247
The local-agent entrypoint registers only three built-in skills
Both mention entrypoint