{"version":"2.1.281","anchor":"new-refusal-reason-claude-desktops-gateway-not-accepted-as","canonical_anchor":"new-refusal-reason-claude-desktops-gateway-not-accepted-as","heading":"New refusal reason: Claude Desktop's gateway not accepted as a managed-settings source","tier":"notice","area":"Managed Settings","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/new-refusal-reason-claude-desktops-gateway-not-accepted-as","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### New refusal reason: Claude Desktop's gateway not accepted as a managed-settings source\n\nA new refusal reason says Claude Desktop's gateway is not an accepted source of managed settings on this machine\n\n**What**\n\nClaude Code has a new reason it can give for refusing managed settings, which are settings an organization pushes to a machine. The reason, `host_gateway_not_accepted`, says that Claude Desktop's gateway is not an accepted source of managed settings on this machine. It is grouped with `unpinned_gateway` and similar reasons.\n\n**Why**\n\nIf settings delivered through Claude Desktop are turned away, you now get a specific explanation instead of a more general one.\n\n- Area: Managed Settings\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5"}