# Claude Code v2.1.270

> Claude Code v2.1.270, released 12 Sep 2026 (2026-09-12). 2 entries read out of the shipped bundle. Unofficial, and not affiliated with Anthropic.

Web version: https://changelogs.core-directive.com/v/2.1.270

This build adds a bypass to the refusal-fallback "silent rearm" system, letting Claude Code re-offer a fallback model for bio-category refusals even after a user has already declined that route. It stays confined to bio-related refusals and remains part of the in-development fallback machinery rather than something a user can trigger directly. The change is not switched on for general use in this release.

## In Development

### Refusal-fallback "silent rearm" can now bypass the declined-route check for bio-category refusals

A new bypass lets Claude Code re-offer a fallback model for bio-related refusals even after the user already declined that route

**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.

**What**

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.

**Why**

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.

- Area: Model Routing
- Tier: Under the hood
- Useful: 3/5
- Signal: 3/5
- Present in the build but not switched on

## Internal Changes

### Release version bump to 2.1.270 propagated through embedded build-metadata literal

Claude Code's version stamp moved to 2.1.270, with a matching new build time and commit SHA

**What**

The build stamp changed from 2.1.269 to 2.1.270. Everywhere Claude Code reports its own version, build time or commit hash now shows the new values, including `--version` output, update-checker messages, user-agent strings, feedback templates, daemon/supervisor logs, remote-control version-gate messages, security-error messages, uninstall-hint text and sourcemap group names.

**Why**

This is a routine release marker update. Nothing about how Claude Code behaves changed, only the numbers and identifiers it reports about itself.

- Area: Elsewhere
- Tier: Under the hood
- Useful: 1/5
- Signal: 0/5