{"version":"2.1.287","anchor":"print-mode-model-override-adoption-now-considers-the-active","canonical_anchor":"print-mode-model-override-adoption-now-considers-the-active","heading":"Print mode compares the model at the start and end of a turn","tier":"notice","area":"Models","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/print-mode-model-override-adoption-now-considers-the-active","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Print mode compares the model at the start and end of a turn\n\nIn print mode, Claude Code now checks the model active at turn start against the one at turn end when deciding whether to adopt a model override\n\n**Unclear.** The exact new rules for when an override is adopted are not shown.\n\n**What**\n\nPrint mode is the way of running Claude Code non-interactively to get a single answer. In print mode, a model override can be adopted during a session. At the end of each turn (one round of request and reply), the logic that decides whether to adopt that override now compares against the model that was active when the turn started. Before, only the override at the start of the turn was recorded.\n\nUsage reporting for this decision also gains a field, `override_same_at_both_ends`.\n\n**Why**\n\nThis addresses an edge case where the model is switched partway through a session, so the model choice at the end of a turn takes into account what was in use when the turn began.\n\n- Area: Models\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}