Claude Code 2.1.239 prices the data-residency premium

Claude Code 2.1.239 folds the 1.1× US-only-inference premium into cost estimates for data-residency workspaces, so /cost, the status line and the --max-budget-usd cap now reflect what those sessions actually cost. The release notes published on Github list more than fifty other changes, most of them fixes.

At a glance

• A proxy that strips the response Content-Type header was making Bedrock streaming fall back to non-streaming on every turn, silently doubling billed API calls; that fallback is fixed.
• The one-time fullscreen renderer offer now reaches Bedrock, Vertex, Foundry and other previously excluded setups, where new installs start in fullscreen, and the prompt stops after three launches when it cannot be answered.
• A new /claude-api upgrade command migrates Python projects from anthropic 0.x to 1.x, and the skill's Python reference now covers 1.x, where timeouts use anthropic.Timeout rather than httpx.Timeout.

Two of these entries point the same way: spend that the client was reporting inaccurately. Data-residency workspaces were being quoted estimates below the billed amount, and the Bedrock proxy fallback was charging twice for work the user saw once. For teams running budget caps or chargeback off the client's own numbers, the corrected figures likely change what those caps allow, and reconciliation against invoices should get easier.

The usage-limit message now names the session and weekly resets

When a monthly spend limit is already exhausted, the usage-limit message now also reports when the session or weekly limit resets. Persistent retry mode, enabled through CLAUDE_CODE_RETRY_WATCHDOG, fails immediately on organization spend-limit and out-of-credits errors instead of waiting indefinitely for a reset.

A request rejected by an organization policy check is no longer re-sent before the rejection reaches the screen. The reminder shown after compaction has been reworked so a skill's original arguments are not re-run as a new request. In VSCode, the View usage control in the usage-limit banner now sits inline with the warning text instead of floating mid-banner.

Bedrock with an SSO profile no longer hangs behind an HTTPS proxy

The credential pre-check used with awsAuthRefresh now honors HTTPS_PROXY, which fixes startups that hung when Bedrock was combined with an SSO profile behind an HTTPS proxy. Starting Claude Code from a directory that no longer exists prints a clear message instead of a raw crash dump, and hooks that failed with posix_spawn ENOENT after the working directory was deleted now run from the project root or the home directory.

Alpine and musl builds ship musl-built binaries for the native image paste, clipboard and audio-capture add-ons, which the runtime previously refused as glibc ones. Edit and Write calls no longer pause for about five seconds in JetBrains IDE terminals with the Claude Code plugin connected, and the Linux sandbox stops breaking sandboxed git commands in repositories with extensions.worktreeConfig set.

Cloud sessions show claude.ai plugins as name@synced

Plugins synced from claude.ai appear in cloud sessions as name@synced, respond to claude plugin enable/disable <name>@synced, and never override a locally installed plugin of the same name. Cloud sessions on the web, desktop and mobile apps no longer resume out of plan mode after an idle worker restart, and remote MCP servers recover from a transient 5xx on a mid-session reconnect or via SDK setMcpServers().

The /resume picker keeps custom session titles past ~64 KB of conversation written after a rename, stops treating a merely reopened session as recently changed, and no longer asks for a cd into a deleted directory such as a removed worktree.

Windows gains cross-session messaging, so sessions across a user's machines can reach each other with SendMessage and ListAgents as on macOS and Linux. ListAgents now reports a session's own name and lists live teammates alongside subagents and other sessions, and a runaway title-syncing loop introduced in 2.1.232 is deduplicated and rate-limited.

What the premium note leaves out The release notes state the multiplier and its scope and nothing more: they give no figure for how much a typical data-residency bill moves once the 1.1× premium is applied, and they do not say whether budgets configured with --max-budget-usd before the update need to be raised. Workspaces outside data residency are not covered by the change.