{"version":"2.1.319","anchor":"claudeai-connector-list-cross-org-override-env-var-and-pag","canonical_anchor":"claudeai-connector-list-cross-org-override-env-var-and-pag","heading":"claude.ai connectors can load with API-key sign-in if you accept a data risk","tier":"use","area":"Connectors","scope":"both","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/claudeai-connector-list-cross-org-override-env-var-and-pag","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### claude.ai connectors can load with API-key sign-in if you accept a data risk\n\nSetting CLAUDE_CODE_I_ACCEPT_CROSS_ORG_DATA_RISK now loads claude.ai connectors when Claude Code uses an API key, with a warning\n\n**What**\n\nConnectors are tools from your claude.ai organization. When Claude Code talked to the model through a different sign-in, such as an API key, connectors were simply turned off. You can now load them anyway by setting the environment variable `CLAUDE_CODE_I_ACCEPT_CROSS_ORG_DATA_RISK`. An environment variable is a named value set before Claude Code starts.\n\n- Claude Code warns that connector tool results go to the organization handling the model.\n\n- The variable is ignored when nonessential network traffic is turned off.\n\n- The list of connectors is now fetched page by page, so long lists load in full.\n\n- Connectors with no directory entry are now marked as such.\n\n**Why**\n\nYou can use your organization's connectors while paying for the model through an API key. Results from those connectors then go to a different organization, which may matter for privacy or company rules.\n\n- Area: Connectors\n- Tier: Use it now\n- Useful: 5\/5\n- Signal: 3\/5\n- Scope: both\n- Heads-up: no"}