Claude Code 2.1.310 brings Monitor to cloud providers and widens Enterprise roles
The 23 October 2026 release adds the Monitor tool on Bedrock, Vertex and Foundry, and new Enterprise role permissions. It affects teams that run Claude Code on a cloud provider.
what changed
Claude Code 2.1.310 was published on 23 October 2026. These changes stand out:
- The Monitor tool and plugin monitors now work on Bedrock, Vertex and Foundry.
- Cloud sessions and Remote Control permissions can now be added to Enterprise custom roles.
- A “Choose file” button loads a cloud environment’s setup script from a file.
- When an MCP tool call times out in a non-interactive session because an elicitation went unanswered, Claude is now told that no answer came and not to repeat the call.
Fixes include requests failing behind gateways that reject the effort-2025-11-24 beta value, and a VS Code bug where pressing Enter on “Send feedback” in plan review approved the plan.
why it matters
Teams that run Claude Code through a cloud provider no longer miss the Monitor tool. Teams that govern access with custom roles can now give cloud sessions and Remote Control to specific groups instead of all or none.
The MCP change helps unattended jobs. A call that waits for a human who is not there used to risk a retry loop. Now Claude is told to stop.
The plan review fix matters if your team uses VS Code. An Enter key press could approve a plan by accident.
what we would do
- If you use Bedrock, Vertex or Foundry, update one pilot machine and try the Monitor tool before you roll it out.
- Review your Enterprise custom roles, and decide who should get cloud sessions and Remote Control.
- If a gateway sits in front of Claude Code, retest requests that failed on the
effort-2025-11-24beta value. - Check any non-interactive job that calls MCP tools with elicitations, and confirm it now stops cleanly.
sources
- Claude Code changelog, version 2.1.310 (Anthropic)
Drafted with Claude from the linked sources, reviewed by us.