{"version":"2.1.223","anchor":"startup-warning-when-claude-code-disable-1m-context-can-t-ac","canonical_anchor":"startup-warning-when-claude-code-disable-1m-context-can-t-ac","heading":"Startup warning when CLAUDE_CODE_DISABLE_1M_CONTEXT can't actually be enforced","tier":"notice","area":"Context Limits","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223\/e\/startup-warning-when-claude-code-disable-1m-context-can-t-ac","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223","markdown":"### Startup warning when CLAUDE_CODE_DISABLE_1M_CONTEXT can't actually be enforced\n\nIf your 1M-context disable flag has no effect on your model, startup now tells you and points at the real setting.\n\n**What**\n\nA second startup notice fires when the 1M-context disable flag is set but the limit is not enforced for the current model.\n\n**Details**\n\n- the notice points you at `CLAUDE_CODE_AUTO_COMPACT_WINDOW`, or the `autoCompactWindow` setting, as the thing that will actually take effect\n- gated on `CLAUDE_CODE_DISABLE_1M_CONTEXT` being set\n- both this and the existing notice are printed at startup, except under json or stream-json output or a background session, where they are written to the log as warnings instead\n\n**Evidence**\n\n`CLAUDE_CODE_DISABLE_1M_CONTEXT is set, but the `\n\n- Area: Context Limits\n- Names: `CLAUDE_CODE_DISABLE_1M_CONTEXT`, `CLAUDE_CODE_AUTO_COMPACT_WINDOW`, `autoCompactWindow`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 0\/5"}