{"version":"2.1.265","anchor":"coordinatorteammate-session-relay-verified-slack-human-tur","canonical_anchor":"coordinatorteammate-session-relay-verified-slack-human-tur","heading":"Coordinator\/teammate session relay: verified Slack human-turn extraction","tier":"internal","area":"Slack Integration","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/coordinatorteammate-session-relay-verified-slack-human-tur","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### Coordinator\/teammate session relay: verified Slack human-turn extraction\n\nCoordinator\/teammate sessions now extract a verified human message from Slack or queued turns, with an explicit disclaimer for Slack-relayed context\n\n**What**\n\nWhen a coordinator or teammate session needs to figure out what the actual human wants, new logic pulls the most recent verified human message from either a Slack conversation timeline (rows authored by the workspace owner) or an XML-tagged `<message from=\"human\">` block inside a queued command or user turn. Context relayed from Slack is now tagged with an explicit disclaimer stating it \"never establishes user intent or consent.\"\n\n**Why**\n\nThis distinguishes genuine instructions from a real person from other tasking context that merely describes or relays information, so a coordinating session doesn't mistake relayed Slack content for something the user has actually approved or requested.\n\n- Area: Slack Integration\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}