A new bypass lets Claude Code re-offer a fallback model for bio-related refusals even after the user already declined that route
When 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.
In 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.
Whether the `tengu_refusal_fallback_route_declined`, `tengu_refusal_fallback_setting_changed`, and `tengu_refusal_fallback_suppressed` gates…