{"version":"2.1.280","anchor":"dialog-bridge-local-only-refusal-fallback-path-reworked","canonical_anchor":"dialog-bridge-local-only-refusal-fallback-path-reworked","heading":"dialog-bridge local-only refusal fallback path reworked","tier":"internal","area":"Elsewhere","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/dialog-bridge-local-only-refusal-fallback-path-reworked","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### dialog-bridge local-only refusal fallback path reworked\n\nClaude Code's fallback dialog for local-only refusals now goes through a different internal function with an explicit local-only flag\n\n**Unclear.** Whether this internal rework changes anything a user would notice, or is purely a behind-the-scenes refactor, is not established by the evidence.\n\n**What**\n\nWhen Claude Code shows a fallback dialog after a refusal and no bridge (a connection to an external dialog handler) is available, it now routes that request through a different internal function than before, and explicitly passes a `localOnly: true` option that this code path did not pass previously.\n\n**Why**\n\nThis is an internal plumbing change to how the local-only refusal fallback dialog is triggered. The finding does not say what user-visible behavior, if any, changes as a result.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}