scaleapi/agentenv-framework

Documentation: www.agentenvframework.com/docs covers environments, artifacts, agents, tasks, the registry and plugins.
## Install
Both packages are on PyPI. You need Python 3.11.4 or newer and, to run environments locally, a running Docker daemon. With uv, install the agent-env command as a tool:
bash
uv tool install agentenv-framework
agent-env run hello
agent-env run hello runs the built-in hello task, which needs no Docker, model or configuration. To try it without installing anything, run it with uvx:
bash
uvx --from agentenv-framework agent-env run hello
Or install it with pip, into a virtualenv:
bash
pip install agentenv-framework
To use the SDK in your own project, add it as a dependency with uv add agentenv-framework. The explorer, agent-env up, needs an .agentenv/config.toml in the current folder or above it; an empty one keeps every local default. Environments and agents run as containers on the local Docker daemon by default; the sandbox docs cover the other sandbox providers and the extra each needs.
A plain install runs on local stores and needs no cloud SDK. The cloud store backends are extras: aws for S3, Secrets Manager, DynamoDB and ECR (pip install 'agentenv-framework[aws]'), and gcp for Cloud Storage, Secret Manager, Firestore and Artifact Registry (pip install 'agentenv-framework[gcp]'). A config that names a backend without its extra fails, naming the extra to install.
The distribution is named agentenv-framework, the import package is agentenv and the command is agent-env. It depends on agentenv-framework-protocol, whose import package is agentenvprotocol, and installs it too.
To work on agent-env itself, install from a clone with uv:
bash
git clone https://github.com/scaleapi/agentenv-framework && cd agentenv-framework
uv sync --extra dev
source .venv/bin/activate
## Plugins
A package of your own can add env types, providers, task steps and stores to agent-env, and agent-env plugin lists, checks, adds and removes installed plugins. The plugin docs show how.
## OpenEnv
Every task in a bundle is an OpenEnv env, with the openenv extra installed (pip install 'agentenv-framework[openenv]'). agentenv.openenv.buildapp(bundle) returns the OpenEnv server for a bundle, a folder or an installed bundle's name, or for a mapping of split names to bundles. Any OpenEnv client resets it to a task, which deploys the task's envs and opens its agent's turn, acts through the envs' tools and an added endturn tool, and gets the task's verifier score as its reward.
## Time zones
Servers and the env clock work in UTC. To run an agent in a user's time zone, the task sets it on the agent's deployagent step as envvars: {"TZ": "America/NewYork"}, which reaches the agent's sandbox, and names the zone in the agent's prompt. While the env clock is armed, the gateway's gettime tool takes that IANA name as timezone and adds the localtime in that zone, and a trigger executor's working hours can take a timezone instead of a fixed utcoffset, so they keep their local hours across daylight-saving changes.
## Contribute, release, license
CONTRIBUTING.md is the contributor guide: open an issue before anything larger than a bug fix, one logical change per pull request with tests, pull request titles in the form type(scope): summary, an approving review from a code owner (CODEOWNERS) and green CI. AGENTS.md is the repository map and conventions file for contributors and coding agents.