{"version":"2.1.302","anchor":"new-hybrid-yields-to-device-policy-unavailability-reason","canonical_anchor":"new-hybrid-yields-to-device-policy-unavailability-reason","heading":"A feature can now step aside silently when you use another provider or a custom URL","tier":"internal","area":"Auth","scope":"both","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302\/e\/new-hybrid-yields-to-device-policy-unavailability-reason","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302","markdown":"### A feature can now step aside silently when you use another provider or a custom URL\n\nA new reason lets some feature quietly turn itself off when you use a third-party provider or a custom base URL, with no message shown\n\n**Unclear.** It is not known which feature this reason turns off.\n\n**What**\n\nClaude Code keeps a list of reasons why a feature might be unavailable. It now has a new one, `hybrid_yields_to_device_policy`. It applies when either of these is true:\n\n- You use a third-party provider, meaning you reach Claude through a service other than Anthropic's own.\n\n- You use a custom base URL, meaning Claude Code sends its requests to an address you chose.\n\nThis reason has no message to show. It is grouped with the existing third-party provider and custom base URL reasons.\n\n**Why**\n\nSome feature now steps aside without telling you when either of those setups is in use.\n\n- Area: Auth\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 4\/5\n- Scope: both\n- Heads-up: no"}