{"version":"2.1.280","anchor":"modelstate-tracks-inline-tools-support-and-repeated-auto-mod","canonical_anchor":"modelstate-tracks-inline-tools-support-and-repeated-auto-mod","heading":"ModelState tracks inline-tools support and repeated auto-mode-unavailable responses","tier":"internal","area":"Elsewhere","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/modelstate-tracks-inline-tools-support-and-repeated-auto-mod","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### ModelState tracks inline-tools support and repeated auto-mode-unavailable responses\n\nClaude Code now tracks repeated 'auto mode unavailable' responses and inline-tool support per session\n\n**Unclear.** The finding does not say what action the stop notice triggers or how many consecutive unavailable responses cause it.\n\n**What**\n\nClaude Code's internal per-session tracker for what a model supports (called ModelState) now keeps additional records:\n\n- whether inline tools (tools called directly within a response, rather than as a separate step) have been refused or confirmed working, via new refused\/emitted flags\n\n- a count of consecutive responses, keyed by a `runKey` identifying a run, where Auto mode reported itself unavailable\n\n- a stop notice that can be set when Auto mode has been unavailable repeatedly\n\n**Why**\n\nThis lets Claude Code notice when Auto mode (automatic model selection) keeps failing to respond in a row and react accordingly, such as surfacing a stop notice, instead of silently retrying forever. It also lets the app remember whether a given model has already confirmed or refused support for inline tool calls, avoiding repeated probing.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}