{"version":"2.1.281","anchor":"remote-managed-settings-separate-ineligible-reason-when-a-h","canonical_anchor":"remote-managed-settings-separate-ineligible-reason-when-a-h","heading":"Remote managed settings: separate ineligible reason when a host gateway isn't accepted","tier":"internal","area":"Managed Settings","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/remote-managed-settings-separate-ineligible-reason-when-a-h","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Remote managed settings: separate ineligible reason when a host gateway isn't accepted\n\nRemote managed settings now report `host_gateway_not_accepted` when a host gateway is rejected\n\n**Unclear.** The finding does not explain what gateway mode or a host verdict is.\n\n**What**\n\nRemote managed settings are settings that an organization supplies to Claude Code from a server. In gateway mode, deciding whether they apply now involves the gateway server's process record, which goes through two checks.\n\nWhen those settings are not allowed, Claude Code gives one of two reasons:\n\n- `host_gateway_not_accepted`: a host verdict exists but was rejected.\n\n- `unpinned_gateway`: every other case, as before.\n\n**Why**\n\nA rejected host gateway now has its own reason, separate from the general `unpinned_gateway` reason, which makes the cause easier to tell apart.\n\n- Area: Managed Settings\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}