{"version":"2.1.274","anchor":"explore-agent-no-longer-inherits-model-cap-on-non-first-part","canonical_anchor":"explore-agent-no-longer-inherits-model-cap-on-non-first-part","heading":"Explore agent no longer inherits model cap on non-first-party providers","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274\/e\/explore-agent-no-longer-inherits-model-cap-on-non-first-part","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274","markdown":"### Explore agent no longer inherits model cap on non-first-party providers\n\nThe Explore agent no longer has its model capped when using non-Anthropic API providers\n\n**What**\n\nThe built-in Explore agent (used for fast, read-only code searches) has logic that decides whether to cap which model it can use, or let it inherit the same model as the main session. That logic now immediately returns \"inherit\" (no cap) whenever the active authentication provider is not Anthropic's own first-party API, before even checking the `CLAUDE_CODE_DISABLE_EXPLORE_INHERIT_CAP` environment variable.\n\n**Why**\n\nUsers connecting through a non-Anthropic provider will have the Explore agent run on the same model as the rest of the session, rather than being capped to a smaller model, regardless of that environment variable's setting.\n\n- Area: Elsewhere\n- Names: `CLAUDE_CODE_DISABLE_EXPLORE_INHERIT_CAP`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}