{"version":"2.1.269","anchor":"new-internal-tracking-flag-toolresultscreeningokemitted","canonical_anchor":"new-internal-tracking-flag-toolresultscreeningokemitted","heading":"New internal tracking flag: toolResultScreeningOkEmitted","tier":"internal","area":"Model Config","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/new-internal-tracking-flag-toolresultscreeningokemitted","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### New internal tracking flag: toolResultScreeningOkEmitted\n\nNew internal flag tracks whether a 'tool result screening OK' signal has been sent this session\n\n**Unclear.** The finding does not say what feature or behavior this tracking flag controls or enables.\n\n**What**\n\nClaude Code keeps some internal per-session bookkeeping about the current model setup. A new boolean field, `toolResultScreeningOkEmitted`, was added to this bookkeeping, along with a pair of functions to check its value and to set it to true, alongside existing tracking fields for tool-change headers and internal safeguards.\n\n**Why**\n\nThis is internal bookkeeping with no described user-facing effect; the finding does not say what feature it supports.\n\n- Area: Model Config\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}