The Lab Notes

Anthropic

Claude Code lets Enterprise Owners gate cloud sessions by role

Claude Code 2.1.310 adds cloud sessions and Remote Control to Enterprise custom roles, so Owners can control access to each by role.

The Lab Notes ·

A brass key ring holding three keys with purple, blue and red heads and yellow blades, on a yellow-green background patterned with pink and green quarter-circle arcs.

Claude Code Enterprise Owners can now control access to cloud sessions and Remote Control by role. Both permissions have been added to Enterprise custom roles.

The change arrived in Claude Code 2.1.310, according to the changelog at code.claude.com. The entry says the permissions were added “so Owners can control access to each by role.” The npm registry lists the release as published Oct. 23, 2026 at 21:20 UTC. Version 2.1.309 came out a day earlier.

The Admin Toggle Now Asks First

Turning on Cloud sessions or Remote Control in admin settings now asks for confirmation. The prompt lists the custom roles that have that permission.

Cloud Environment Dialogs Get Reworked

The cloud environment dialog now opens network access, the setup script and environment variables from rows instead of listing every editor at once. A new Choose file button loads a setup script from a file.

The release also fixes how errors appear. Failed saves and archives in the cloud environment edit dialog previously showed no error inside the dialog. Failed routine API token actions showed only a toast. The error now appears in the routine edit dialog. The session start checklist now shows a cloud environment’s setup script output in a scrolling box.

Monitor Tool Reaches More Setups

Claude Code 2.1.310 adds the Monitor tool and plugin monitors on Bedrock, Vertex and Foundry. They also work when telemetry or nonessential traffic is disabled. Long foreground sleeps are now blocked in those setups too.

Our View

We think the useful detail is that the confirmation prompt names the custom roles that hold each permission. Cloud sessions and Remote Control are now tied to roles. An Owner can give one to a custom role and leave it off another.

That changes what an Owner sees at the switch. Turning either feature on in admin settings shows which custom roles already carry it. The Owner can confirm or back out with that list in view.

Developers feel the change too. An Owner can now set access to cloud sessions and Remote Control per role. The custom role a developer holds can decide whether they get either one.

The control works as intended only if custom roles match the people an Owner means to cover.