{"version":"2.1.234","anchor":"groundwork-for-a-slack-tagging-integration-present-but-inert","canonical_anchor":"groundwork-for-a-slack-tagging-integration-present-but-inert","heading":"Groundwork for a Slack tagging integration, present but inert","tier":"soon","area":"Slack Integration","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/groundwork-for-a-slack-tagging-integration-present-but-inert","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### Groundwork for a Slack tagging integration, present but inert\n\nSession and message records now carry Slack tagging plumbing, but nothing turns it on.\n\n**What**\n\nSession state and message records now carry the plumbing for connecting Claude Code to Slack tagging, including a connection flag, an environment variable for a token, and a per-message ownership marker. Every piece is wired through to storage and to the tool-selection path, but nothing in this build ever turns any of it on, and no tool or user-facing surface appears as a result.\n\n**Details**\n\n- Interactive sessions carry a boolean `slackTagConnected`, defaulting to false at every point a session is created.\n- `slackTagConnected` can be set through the state-patch path and over the control protocol that SDK and IDE clients use, and is read by a status selector.\n- That same flag forms part of the key used to memoise the list of available tools, so flipping it would recompute which tools are offered.\n- A `CLAUDE_CODE_SLACK_TAG_TOKEN` environment variable is read for credentials.\n- Individual messages carry a `slackTagOwnerTurn` marker that is written through into stored transcripts, but the code that would set it is absent here.\n- None of these fields existed in the previous release.\n\n**Evidence**\n\n`slackTagConnected`, `slackTagOwnerTurn`\n\n- Area: Slack Integration\n- Names: `CLAUDE_CODE_SLACK_TAG_TOKEN`\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 5\/5\n- Present in the build but not switched on"}