If your 1M-context disable flag has no effect on your model, startup now tells you and points at the real setting.
What's wrong with this entry?
A second startup notice fires when the 1M-context disable flag is set but the limit is not enforced for the current model.
- the notice points you at
CLAUDE_CODE_AUTO_COMPACT_WINDOW, or theautoCompactWindowsetting, as the thing that will actually take effect - gated on
CLAUDE_CODE_DISABLE_1M_CONTEXTbeing set - 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
CLAUDE_CODE_DISABLE_1M_CONTEXT is set, but the
Strings lifted out of the shipped bundle, so the claim above can be checked against them.