{"version":"2.1.321","anchor":"claude-security-added-to-a-connector-list","canonical_anchor":"claude-security-added-to-a-connector-list","heading":"The name claude-security now sits in a list of known connectors","tier":"internal","area":"Connectors","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/claude-security-added-to-a-connector-list","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### The name claude-security now sits in a list of known connectors\n\nClaude Code now lists `claude-security` alongside Salesforce, Sentry and Snowflake in one of its connector name lists\n\n**Unclear.** What this list controls, and so what including `claude-security` changes for a user, is not known.\n\n**What**\n\nClaude Code keeps a list of connector names that includes Salesforce, Sentry and Snowflake. A connector is an outside service Claude Code can talk to. The name `claude-security` now appears in that list too. The name was already used elsewhere in Claude Code before this build.\n\n**Why**\n\nWhatever Claude Code does with the other names in this list, it now does with `claude-security` as well. This may mean it is treated as a built-in connector or as an allowed one.\n\n- Area: Connectors\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}