A Slack connection flag, token env var and per-message ownership marker are wired through storage with no surface.
What
Session 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.
Details
- Interactive sessions carry a boolean
slackTagConnected, defaulting to false at every point a session is created. slackTagConnectedcan 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.- 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.
- A
CLAUDE_CODE_SLACK_TAG_TOKENenvironment variable is read for credentials. - Individual messages carry a
slackTagOwnerTurnmarker that is written through into stored transcripts, but the code that would set it is absent here. - None of these fields existed in the previous release.
Evidence
slackTagConnected, slackTagOwnerTurn
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Names in the bundleCLAUDE_CODE_SLACK_TAG_TOKEN
One source agreesOne thing we can check says the same as this entry.
The name it cites is new in this build
New in this build: CLAUDE_CODE_SLACK_TAG_TOKEN