Follow Discord
Sweep 06 Nov 2026 · 01:32Z Build v2.1.319 537 read Stable v2.1.311 Latest v2.1.318 Next v2.1.319 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.275 ·

Fallback model config now seeded to remote sessions

Fallback model setting is now passed to remote sessions when running under CLAUDE_CODE_REMOTE

Under the hood Internal Changes
JSON All of v2.1.275
Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
SessionsArea: what it touches
Internal ChangesKind: in v2.1.275,
Internal ChangesSection of the release
What

When Claude Code is running under the CLAUDE_CODE_REMOTE environment variable, the resolved fallback-model setting (the backup model used when the primary model is unavailable) is now passed into the remote-control path as well.

Why

This keeps a remotely-run session's fallback model configuration in sync with the rest of its setup, rather than leaving it unset in that path.

Read from
Names in the bundleCLAUDE_CODE_REMOTE
What the documentation says
Since it was published

The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.

Confirmed since Anthropic's documentation has since written up CLAUDE_CODE_REMOTE, on Monitoring. By default, metrics and events from a cloud session carry the [standard attributes](#standard-attributes), including `session.id`, `ccr.session.id`, and `organization.id`, so you can filter by session or organization without extra configur… monitoring-usage see the edit
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up CLAUDE_CODE_REMOTE, on Monitoring.

See this entry in the whole of v2.1.275 →

Feedback