{"version":"2.1.314","anchor":"repo-settings-can-no-longer-set-provider-managed-env-vars-be","canonical_anchor":"repo-settings-can-no-longer-set-provider-managed-env-vars-be","heading":"Repository settings cannot set provider-managed variables beside an organization connection","tier":"notice","area":"Managed Settings","scope":"org","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/repo-settings-can-no-longer-set-provider-managed-env-vars-be","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Repository settings cannot set provider-managed variables beside an organization connection\n\nWith an organization connection, project and repository settings can no longer set provider-managed environment variables\n\n**Unclear.** Nothing says which setups count as running beside an organization's connection.\n\n**What**\n\nSettings files can set environment variables, which are named values Claude Code reads when it starts. When Claude Code is running beside your organization's connection, settings that come from a project or repository can no longer set the variables your provider manages. If they try, Claude Code logs a warning: \"beside your organization's connection, a repository's settings don't set provider-managed variables.\"\n\nOn desktop hosts, organization policy settings may set `CLAUDE_CODE_CERT_STORE`, which chooses where Claude Code finds its trusted certificates.\n\n**Why**\n\nA repository you open cannot quietly change how Claude Code connects through your organization. If a project's settings used to set these variables, they will now be ignored and you will see a warning.\n\n- Area: Managed Settings\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: org\n- Heads-up: yes"}