{"version":"2.1.234","anchor":"slack-tagging-wiring-in-the-environment-status-line-and-tool","canonical_anchor":"slack-tagging-wiring-in-the-environment-status-line-and-tool","heading":"Slack tagging wiring in the environment, status line and tool refresh","tier":"soon","area":"Slack Integration","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/slack-tagging-wiring-in-the-environment-status-line-and-tool","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### Slack tagging wiring in the environment, status line and tool refresh\n\nA Slack tag token env var is treated as auth, stripped from subprocesses, and gets a status-line segment.\n\n**What**\n\nA `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.\n\n**Details**\n\n- The status segment only renders when the session is marked connected, which nothing in this build does.\n\n**Evidence**\n\n`CLAUDE_CODE_SLACK_TAG_TOKEN`\n\n- Area: Slack Integration\n- Names: `CLAUDE_CODE_SLACK_TAG_TOKEN`\n- Tier: Nothing to try yet\n- Useful: 3\/5\n- Signal: 5\/5\n- Present in the build but not switched on"}