{"version":"2.1.237","anchor":"verified-human-marker-for-slack-relayed-turns-plus-a-stubbed","canonical_anchor":"verified-human-marker-for-slack-relayed-turns-plus-a-stubbed","heading":"Verified-human marker for Slack-relayed turns, plus a stubbed third relay surface","tier":"notice","area":"Slack Integration","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.237\/e\/verified-human-marker-for-slack-relayed-turns-plus-a-stubbed","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.237","markdown":"### Verified-human marker for Slack-relayed turns, plus a stubbed third relay surface\n\nSlack turns from a server-verified human get a marker so Claude treats them as you without extra confirmation.\n\n**What**\n\nTurns 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.\n\n**Details**\n\n- The paragraph replaces the previous cross-session messages rule in the prompt.\n- 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.\n\n**Evidence**\n\n`[Verified human message relayed from the bound Slack thread]:`\n\n- Area: Slack Integration\n- Names: `CLAUDE_CODE_ENTRYPOINT`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 4\/5"}