{"version":"2.1.301","anchor":"model-capability-lookups-skipped-under-a-different-predicate","canonical_anchor":"model-capability-lookups-skipped-under-a-different-predicate","heading":"Different conditions now decide when saved model capability data is used","tier":"internal","area":"Models","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301\/e\/model-capability-lookups-skipped-under-a-different-predicate","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301","markdown":"### Different conditions now decide when saved model capability data is used\n\nClaude Code changed the checks that decide when it reads or uses its saved record of what each model can do\n\n**Unclear.** It is not clear under which conditions the lookups now stop early, so the effect on any given setup is unknown.\n\n**What**\n\nClaude Code keeps a saved record of what each model can do. The checks that decide when it reads that record, looks something up in it, or deletes an entry from it have changed. Some lookups and deletions now stop early in cases where they did not before.\n\n**Why**\n\nThis could change when that saved model information is used.\n\n- Area: Models\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}