{"version":"2.1.229","anchor":"1m-context-models-no-longer-suppressed-on-custom-endpoints","canonical_anchor":"1m-context-models-no-longer-suppressed-on-custom-endpoints","heading":"1M-context models no longer suppressed on custom endpoints","tier":"use","area":"Models","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229\/e\/1m-context-models-no-longer-suppressed-on-custom-endpoints","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229","markdown":"### 1M-context models no longer suppressed on custom endpoints\n\nSubscription users on a custom base URL now see the 1M-context model variants again.\n\n**What**\n\nThe `[1m]` long-context model variants were hidden from subscription accounts whose credit state disallowed extra usage. That credit check now applies only when you are talking to Anthropic's own endpoints or a local socket, so subscription users pointed at a custom `ANTHROPIC_BASE_URL` see the 1M variants offered. Setting `CLAUDE_CODE_DISABLE_1M_CONTEXT` still hides them everywhere.\n\n**Details**\n\n- The first-party test is satisfied by `ANTHROPIC_UNIX_SOCKET` being set, or by the base URL being an Anthropic one.\n- On first-party endpoints behaviour is unchanged: cached extra-usage state still decides.\n\n**Evidence**\n\n`CLAUDE_CODE_DISABLE_1M_CONTEXT`\n\n- Area: Models\n- Names: `ANTHROPIC_BASE_URL`, `CLAUDE_CODE_DISABLE_1M_CONTEXT`, `[1m]`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 3\/5"}