{"version":"2.1.299","anchor":"policy-managed-claude-code-attribution-header-is-protected-f","canonical_anchor":"policy-managed-claude-code-attribution-header-is-protected-f","heading":"Managed settings can hold their CLAUDE_CODE_ATTRIBUTION_HEADER value against a host program","tier":"notice","area":"Managed Settings","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/policy-managed-claude-code-attribution-header-is-protected-f","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Managed settings can hold their CLAUDE_CODE_ATTRIBUTION_HEADER value against a host program\n\nUnder some conditions, the managed-settings value of `CLAUDE_CODE_ATTRIBUTION_HEADER` now wins over one passed in by the program that starts Claude Code\n\n**Unclear.** The conditions under which the managed value wins are not stated.\n\n**What**\n\n`CLAUDE_CODE_ATTRIBUTION_HEADER` controls whether Claude Code includes the attribution block. Managed settings are settings an organisation's administrator puts on a machine. When another program starts Claude Code and passes in its own environment variables, the managed-settings value of `CLAUDE_CODE_ATTRIBUTION_HEADER` can now win over the value that program supplies, when certain conditions hold. Before, there was no such exception.\n\n**Why**\n\nAdministrators can fix this setting so that programs which launch Claude Code cannot change it.\n\n- Area: Managed Settings\n- Names: `CLAUDE_CODE_ATTRIBUTION_HEADER`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: org\n- Heads-up: no"}