{"version":"2.1.222","anchor":"model-refusal-fallback-events-gain-a-scope-field","canonical_anchor":"model-refusal-fallback-events-gain-a-scope-field","heading":"model_refusal_fallback events gain a scope field","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.222\/e\/model-refusal-fallback-events-gain-a-scope-field","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.222","markdown":"### model_refusal_fallback events gain a scope field\n\nModel fallback events now say whether the swap affects your whole session or just one subagent.\n\n**What**\n\nFallback events now distinguish a session-wide model swap from a one-off fallback in a subagent or side question, so consumers can tell how far the change reaches.\n\n**Details**\n\n- The SDK schema adds an optional `scope` enum with values \"session\" and \"local\".\n- \"session\" means the main thread swapped models for the rest of the session; \"local\" means only a subagent, a \/btw side question or a background fork fell back.\n- The field is absent from older CLIs and should be treated as \"session\" when missing.\n- The event builder sets `scope` and selects different wording for local fallbacks.\n\n**Evidence**\n\n`'local': a subagent \/ side-question (\/btw) \/ background fork fell back`\n\n- Area: Elsewhere\n- Names: `\/btw`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 0\/5"}