Eden

Python orchestrator for AI coding agents in sandboxed git worktrees.

Eden creates a fresh git worktree on a new branch, runs a coding agent (Claude Code, Codex, opencode, pi, or any line-streaming CLI) inside a sandbox (Docker, Podman, isolated, Daytona, Vercel, or forkd microVMs), captures its output, and commits the changes back. You get a branch with one clean commit per iteration, ready to review or merge.

flowchart LR
    Repo[(Host repo)] --> WT[Fresh worktree<br/>on new branch]
    WT --> SB[Sandbox<br/>docker • podman • isolated<br/>daytona • vercel • forkd • no_sandbox]
    SB --> Agent[Coding agent<br/>claude_code • codex<br/>opencode • pi • cli_agent]
    Agent -->|stdout stream| Loop{iteration loop}
    Loop -->|commit per iteration| Branch[Eden branch]
    Loop -->|next iteration| Agent
    Branch --> Repo

Loading

Install

pip install eden-agent

Requires Python 3.11+.

Quick example

The simulated_agent runs without any external CLI installed. Run this from inside a git repository:

from pathlib import Path

from eden import run, simulated_agent
from eden.sandboxes.no_sandbox import provider as no_sandbox

result = run(
    cwd=Path.cwd(),
    sandbox=no_sandbox(),
    agent=simulated_agent(
        output="hello from the simulated agent\n<promise>COMPLETE</promise>\n",
    ),
    prompt="ignored by the simulated agent",
    max_iterations=1,
)

print(f"branch: {result.branch}")
print(f"iterations: {len(result.iterations)}")

For a real agent, scaffold a project:

eden init --sandbox docker --agent claude-code --yes
cp .eden/.env.example .env  # then fill in API keys
docker build -t eden:$(basename $(pwd)) -f .eden/Dockerfile .
python .eden/main.py

Development with Flox

Eden uses Flox in two distinct ways — don't conflate them:

1. The repo dev toolchain — the .flox/ environment that sets up your machine to work on Eden.
2. Per-agent runtimes — an optional, separate environment each agent declares for its own CLI.

Repo dev toolchain

On Linux/macOS the repo ships a declarative, lockfile-pinned dev environment under .flox/. With Flox installed:

flox activate # provisions toolchain + builds .venv on first run
pytest -m "unit or e2e"
pre-commit run --all-files

flox activate provides Python 3.11/3.12/3.13, git, gh, the docker/podman clients, pre-commit, and make, then builds .venv via pip install -e ".[dev]". Pick the interpreter with EDEN_PYTHON (e.g. EDEN_PYTHON=python3.12 flox activate; defaults to python3.11).

Flox is Linux/macOS only — on Windows, install directly with python -m pip install -e ".[dev]". See AGENTS.md for the full command list.

Per-agent runtimes

Separately, each agent can declare its own Flox runtime via flox_env= on its factory. Eden then runs that agent's CLI inside flox activate -d <dir> -- <argv>, so the agent gets a declared, lockfile-pinned toolchain instead of inheriting the host's. See Agents — Per-agent Flox runtime.

Documentation

Full documentation lives in docs/:

• What is Eden? — positioning and feature matrix
• Quick start — five-minute tour
• Tutorial: build your first agent loop — 10-minute walkthrough that ends with a real agent fixing a real bug
• Python API reference — every name importable from eden
• How it works — branch strategies, sandbox lifecycle, iteration loop
• Sandbox providers — seven provider catalog
• Agents — six agent factories

License

PolyForm Shield 1.0.0.