Introducing Claude Environments in Obot

Introducing Claude Environments in Obot

Claude can investigate issues, work with code, and call the services your team depends on. Giving it that access raises a few questions: Who can use the environment? Which tools and services can they reach? How are credentials handled? How can we audit user’s activity?

Obot v0.27.0 introduces Claude Environments, an experimental feature that brings those controls together. Your team keeps working in Claude, and sessions running on your Kubernetes infrastructure with access managed through Obot.

Read the full details on the v0.27 release here.

Visible in Claude. Authorized by Obot.

When you create a self-hosted environment in Claude, it appears for every user in your Claude organization. There is no distinction in that list between the people you intend to use an environment and everyone else.

Seeing an Obot-hosted environment in Claude does not grant permission to use it. Obot will check the user’s identity and access before provisioning the session and denies requests from users who have not been granted access.

Administrators define that access through profiles. A profile connects users or groups to an environment, the vMCPs they can use, their allowed network destinations, and their resource limits.

For example, an engineering profile could give developers access to documentation and issue-tracking tools, allow requests to an internal API, and provide the resources needed to build and test code. Another profile for the sales team can grant access to HubSpot, Excel, and have lower resource requirements for less intensive tasks.

Claude accounts map to Obot users, and existing vMCP permissions still apply. An environment profile does not bypass the controls you have already put around your tools.

Introducing Claude Environments in Obot

Your tools available inside the session

Claude Environments builds on Obot’s virtual MCP servers. The tools you have already organized into vMCPs can be made available to sessions through their profiles.

An engineer investigating a bug could ask Claude to read the issue, search internal documentation, and work on a solution. Those tool calls use the engineer’s mapped Obot identity and permissions.

Obot also handles the credentials for those connections. The session’s configuration contains a placeholder, and the egress gateway supplies a short-lived, user-scoped credential when it connects to the appropriate Obot endpoint. The actual Obot credential stays out of the runner’s configuration.

That same approach extends to other HTTP services. Administrators can configure a secret header for a specific destination, and the gateway injects it into HTTPS requests to that host. A session can call an internal API without having its real token placed in the session configuration so the agent never sees your secret data.

Control beyond MCP

Agents do more than call MCP tools. They download dependencies, fetch URLs, and make API requests. Claude Environments lets you control those destinations, too.

Administrators configure allowed hosts for the environment, with profiles adding destinations for teams that need them. An engineering session might need package registries and development services; another group might need a much smaller set of destinations.

Network access and credentials are separate controls. Adding a credential for a service does not automatically make that service reachable. Administrators can update both network policies and injected secrets for running sessions as requirements change and those changes will be automatically reflected by new and existing sessions.

A view of the work behind the conversation

Users continue chatting in Claude, while Obot provides visibility into the sessions behind those conversations.

Users can find their own sessions, and administrators can inspect activity across the organization, see the associated users and repositories, and suspend or delete sessions. Idle sessions can suspend with their workspace saved, ready to restore when work resumes. This frees up resources for other sessions to run.

The Claude Environments audit view records HTTP and HTTPS activity passing through the egress gateway. Administrators can follow requests back to a user and session, see their destinations and outcomes, and investigate denied requests. Request and response payloads require additional auditor access, and capture limits are documented.

Introducing Claude Environments in Obot

This gives administrators a place to answer practical questions: Which session called this service? Whose access did it use? Why was that request blocked?

From a conversation to a shared workflow

Claude Tag sessions started from Slack or GitHub can use these environments as well. A team can route those tasks into an environment with the tools and network access needed for the job.

Claude Tag uses a dedicated service identity with its own assigned permissions. Everyone who triggers that workflow uses that identity’s access, so administrators can define a consistent scope for shared tasks such as investigating issues or answering questions with internal tools.

Admins can configure Claude Tag sessions to use Obot-hosted environments by following Anthropic’s documentation.

What runs where

Obot uses Agent Substrate to run isolated sessions on Kubernetes and manage workspace suspension and restoration. Users select the environment in Claude, then Obot checks access, gathers configuration and provisions the execution environment.

Connections to Anthropic are outbound, so Anthropic does not need an inbound connection into your cluster. That means Obot-hosted environments work behind firewalls or on localhost. Execution takes place on your infrastructure, while inference and session communication—including prompts, responses, and tool results—still reach Anthropic.

Try Claude Environments

Claude Environments is experimental and disabled by default in Obot v0.27.0. It requires a compatible Kubernetes deployment with additional resources and configuration, plus a Claude Team or Enterprise organization with self-hosted environments enabled.

Start with the v0.27.0 release notes and Obot documentation to connect an environment and configure your first profile. We’d love to hear what your team builds with it.

Related Articles

⌂