OpenEnv documentation
Getting Started
Getting Started
Install OpenEnv, load an environment, and run your first step.
Install OpenEnv
pip install openenv
This installs the full OpenEnv runtime: the environment server, the client, the
openenvCLI, the web interface, and MCP support. Environments depend onopenenvdirectly.
Optional dependencies
A few integrations ship as optional extras. Install them with
pip install openenv[<extra>]:
| Extra | Pulls in |
|---|---|
inspect | The Inspect AI evaluation harness |
daytona, aca, modal | Cloud sandbox providers (see the Core API reference) |
Try an Environment
Use AutoEnv and AutoAction when you want OpenEnv to find the matching client
and action classes for an installed or discoverable environment.
from openenv import AutoAction, AutoEnv
env = AutoEnv.from_env("echo")
EchoAction = AutoAction.from_env("echo")
with env.sync() as client:
result = client.reset()
print(result.observation.echoed_message) # "Echo environment ready!"
result = client.step(EchoAction(message="Hello, OpenEnv!"))
print(result.observation.echoed_message) # "Hello, OpenEnv!"AutoEnv.from_env() accepts the common name forms:
AutoEnv.from_env("echo")
AutoEnv.from_env("echo-env")
AutoEnv.from_env("echo_env")Connect to a Running Environment
OpenEnv clients are async by default. Use the async client for production code, parallel environment runs, and integrations with async frameworks.
import asyncio
from echo_env import CallToolAction, EchoEnv
async def main():
async with EchoEnv(base_url="https://openenv-echo-env.hf.space") as client:
await client.reset()
result = await client.step(
CallToolAction(
tool_name="echo_message",
arguments={"message": "Hello, World!"},
)
)
print(result.reward)
asyncio.run(main())For scripts and notebooks, use .sync():
from echo_env import CallToolAction, EchoEnv
with EchoEnv(base_url="https://openenv-echo-env.hf.space").sync() as client:
client.reset()
result = client.step(
CallToolAction(
tool_name="echo_message",
arguments={"message": "Hello, World!"},
)
)
print(result.observation.result)Use Containers or Local Servers
You can run an environment from a Docker image:
import asyncio
from echo_env import EchoEnv
async def main():
client = await EchoEnv.from_docker_image(
"registry.hf.space/openenv-echo-env:latest"
)
async with client:
result = await client.reset()
print(result.observation)
asyncio.run(main())If you run the Hugging Face Space image yourself with docker run, expose port
7860 and connect to that port:
docker run -it -p 7860:7860 --platform=linux/amd64 \
registry.hf.space/openenv-echo-env:latestfrom echo_env import EchoEnv
with EchoEnv(base_url="http://localhost:7860").sync() as client:
result = client.reset()Or connect to a local server:
cd path/to/echo-env
uv venv
source .venv/bin/activate
uv pip install -e .
uv run server --host 0.0.0.0 --port 8000from echo_env import EchoEnv
with EchoEnv(base_url="http://localhost:8000").sync() as client:
result = client.reset()Cloud sandbox providers implement the same ContainerProvider contract as
local Docker: they start an isolated environment server and return a base_url
that an EnvClient can connect to directly, while keeping provider-specific
control-plane concepts (sandbox groups, projects, signed URLs, snapshots, egress
policy) inside the provider. Because the contract is provider-neutral, any hosted
runtime can implement it without changing the client/server protocol.
Providers shipped today: LocalDockerProvider, DockerSwarmProvider,
UVProvider, DaytonaProvider, and ACASandboxProvider (Azure Container Apps
Sandboxes). A KubernetesProvider is planned.
See the Runtime Providers guide for the full list, install extras, and how to select a provider, and the Core API reference for each provider’s API. The provider-neutral invariants are described in the Cloud Sandbox Providers amendment proposed in RFC 002 (env-spec).