envctl documentation

One stack per branch. Two people or ten agents on one machine, no port fights, no shared database.

Pick your path

You run the stack by hand

You already type docker compose up. envctl keeps that workflow and gives every worktree its own project, network, volumes, and ports.

You run coding agents in worktrees

Two hooks make every Claude Code worktree self-provisioning: the environment starts when the worktree is created and is destroyed when it goes.

Already running a coding agent in this repo? Paste this prompt:

Help me set up envctl for this repository. Read docs/public/agent-guide.md in the envctl repo first, then walk me through it.

The guide teaches the agent the manifest, the commands, and the common fixes, so its answers stay accurate.

Concepts

Features, environments, port modes, and the rendered project, in two minutes.

Configuration

Write envctl.yaml, choose a port mode, expose entrypoints, and point host tooling at the env file.

Your first workflow

Take one feature from an objective to a reviewed pull request, with agents working in an isolated VM.

CLI reference

Every command, flag, and output shape, including --json for scripts and agents.

Roadmap

Bubble Tea workflows, executable planning, invocation plugins, isolated VMs, and teammate sharing, in build order.