{"version":"2.1.270","anchor":"refusal-fallback-silent-rearm-can-now-bypass-the-declined","canonical_anchor":"refusal-fallback-silent-rearm-can-now-bypass-the-declined","heading":"Refusal-fallback \"silent rearm\" can now bypass the declined-route check for bio-category refusals","tier":"internal","area":"Model Routing","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.270\/e\/refusal-fallback-silent-rearm-can-now-bypass-the-declined","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.270","markdown":"### Refusal-fallback \"silent rearm\" can now bypass the declined-route check for bio-category refusals\n\nA new bypass lets Claude Code re-offer a fallback model for bio-related refusals even after the user already declined that route\n\n**Unclear.** Whether the `tengu_refusal_fallback_route_declined`, `tengu_refusal_fallback_setting_changed`, and `tengu_refusal_fallback_suppressed` gates are enabled is unread, not established either way.\n\n**What**\n\nWhen Claude's response is stopped by a 'refusal' (the API declining to answer) and Claude Code considers switching to a fallback model, it normally avoids re-suggesting a route the user or session already turned down. This release adds an exception: if the server-side routing found no match, the refusal is categorized as `\"bio\"`, and a refusal fallback hasn't already happened this session, Claude Code can now recompute and re-arm a fallback model for that route even though it was previously declined. This works through a new `visibleRouteDeclined` option that, when set, skips the usual check that would otherwise block re-arming an already-declined route.\n\n**Why**\n\nIn practice this means bio-category refusals get an extra chance at being rerouted to a fallback model instead of being permanently blocked once a route is declined once. Three related settings, `tengu_refusal_fallback_route_declined`, `tengu_refusal_fallback_setting_changed`, and `tengu_refusal_fallback_suppressed`, are tied to this behavior, but nothing is yet known about how they're currently configured.\n\n- Area: Model Routing\n- Tier: Under the hood\n- Useful: 3\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}