{"version":"2.1.265","anchor":"new-remote-config-flag-tagconnectorwrites-adds-a-slackcl","canonical_anchor":"new-claude-tag-connector-writes-system-prompt-clause-for-s","heading":"New 'Claude Tag connector writes' exception for Slack-delegated sessions, gated off","tier":"internal","area":"Slack Integration","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/new-remote-config-flag-tagconnectorwrites-adds-a-slackcl","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### New 'Claude Tag connector writes' exception for Slack-delegated sessions, gated off\n\nA new remote-config flag lets Slack-delegated sessions write through specific connector tools without a visible user request, currently disabled\n\n**What**\n\n- For sessions started from Slack (referred to as \"Claude Tag\"), a new system-prompt block lists the session's connector MCP tool name prefixes and tells the model that writes through those specific tools aren't blocked merely for lacking a visible user request in the transcript.\n\n- Hard blocks still apply: credential\/secret exposure, destructive actions, permission changes, and messaging others are still enforced.\n\n- The block is controlled by a new remote-config flag, `tagConnectorWrites`, which currently defaults to off (`false`).\n\n**Why** Slack-delegated sessions often act on a connector tool without an explicit chat request behind each individual write; this exception is meant to stop the security monitor from blocking those legitimate writes, while keeping the more serious hard blocks in place. It isn't turned on yet.\n\n- Area: Slack Integration\n- Names: `tagConnectorWrites`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}