DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to run local environments in the explorer with Agentenv Framework

Start the explorer on your own Docker daemon using the all-local config.

Who it is forAn RL researcher or engineer who wants to build and inspect environments on a laptop or workstation before sharing them.

The problemYou need a local setup where environments and agents run as containers, with a visual explorer to look at them.

The outcomeThe explorer starts with the all-local configuration, and environments and agents run as containers on your Docker daemon.

What you need first

  • Python 3.11.4 or newer
  • uv (https://docs.astral.sh/uv/) or pip
  • A running Docker daemon for running environments locally

Steps

  1. Make sure a Docker daemon is running on your machine.
  2. Copy .agentenv/config.example.toml to .agentenv/config.toml in your project folder. (inferred, check the README)
  3. Run uv tool install 'agentenv-framework[explorer]'.
  4. Run agent-env up from your project folder or a folder below it.

Prompt for your agent

In the scaleapi/agentenv-framework repo, prepare <project folder> with an .agentenv/config.toml copied from .agentenv/config.example.toml, then run `agent-env up`. Report the address or message the explorer prints and whether it started. Verify that the Docker daemon is reachable before you start.

Caveat. The explorer needs the explorer extra and a config file in the current folder or above it; an empty config file keeps every local default.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page