A Slack tag token env var is treated as auth, stripped from subprocesses, and gets a status-line segment.
CLAUDE_CODE_SLACK_TAG_TOKEN and a slack-tag status segment exist, but nothing enables the connection.
What's wrong with this entry?
A CLAUDE_CODE_SLACK_TAG_TOKEN environment variable now counts as third-party authentication and is stripped from environments given to spawned commands. The status line gained a slack-tag segment, which suppresses the separator dot the way the bridge and pr segments do, and the available tool set is recomputed whenever the Slack tag connection flag changes.
- The status segment only renders when the session is marked connected, which nothing in this build does.
CLAUDE_CODE_SLACK_TAG_TOKEN
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.237
Verified-human marker for Slack-relayed turns, plus a stubbed third relay surface
Both mention slack integration