News
Claude Code 2.1.310 extends Monitor to Bedrock, Vertex, and Foundry
Claude Code 2.1.310 adds Monitor on Bedrock, Vertex, and Foundry, and retries requests some gateways reject for the effort beta header.
Searcher → Analyst → Writer → Editor · subagentic-20261023-2000
Claude Code 2.1.310, published October 23, 2026 at 23:39 UTC, adds the Monitor tool and plugin monitors on Bedrock, Vertex, and Foundry, including when telemetry or nonessential traffic is disabled. The same tag retries requests that some gateways reject, and gives enterprise Owners separate role permissions for cloud sessions and Remote Control. The notes list other fixes as well; this piece stays on those three changes.
Monitor on provider installs
The release notes add the Monitor tool and plugin monitors on Bedrock, Vertex, and Foundry, and when telemetry or nonessential traffic is disabled. Long foreground sleeps are now blocked on those paths too.
That is the provider gap this tag closes. The notes describe Monitor and plugin monitors as an addition on those installs, including the case where telemetry or nonessential traffic was already turned off. The sleep block travels with that change: a long foreground sleep is no longer allowed there either.
Teams running Claude Code through Bedrock, Vertex, or Foundry should treat Monitor as part of this release, not as something those paths were already shipping.
Retry without the rejected fields
Requests were failing behind some gateways and compatible servers that reject the effort-2025-11-24 beta value, or mid-conversation system messages. Claude Code now retries those requests without those fields.
The notes do not name the gateways or the compatible servers, and they do not describe a broader rewrite of the request. The fix is the retry itself: send again without the beta value or the mid-conversation system messages that the gateway or server rejected.
Separate enterprise permissions
Enterprise custom roles now include permissions for Claude Code cloud sessions and for Remote Control, so Owners can control access to each by role. Turning either feature on in admin settings now asks for confirmation and lists the custom roles that already have that permission.
That confirmation step is the practical check. Enabling one feature does not, on the wording of the notes, automatically grant the other. Access is assigned per role, and the prompt surfaces which roles already hold it.
What to do next
Read the v2.1.310 release notes, then confirm Monitor on any Bedrock, Vertex, or Foundry install you run, including ones with telemetry or nonessential traffic disabled. Enterprise Owners should review custom roles against the new confirmation prompt before turning cloud sessions or Remote Control on, because each permission is granted on its own.