Network-aware local workflows
VibePod 0.3.0 added a --network option to vp run, letting an agent container join an additional Docker network. It also added compose-file detection: when a workspace contains docker-compose.yml or compose.yml, the CLI can prompt for a running project network and connect the agent container to it.
This made local agent sessions more useful for real projects, because the agent could run beside databases, app containers, and other services already running through Docker Compose.
Documentation and packaging polish
The release added PyPI installation guidance to the README and introduced the first MkDocs documentation structure, including quickstart, agents, configuration, CLI reference, and development pages. It also added GitHub workflows for CI and docs publishing, then refined the CI matrix and repository paths.
What 0.3.1 fixed
The 0.3.1 patch added README shields, extended the docs publishing workflow, and removed direct port binding from the proxy container so the proxy setup fit better into VibePod's Docker-network model.
Example commands
The 0.3 line made agent containers easier to connect to project networks and documented PyPI installation.
pip install vibepod
# Attach an agent container to a known Docker network:
vp run claude --network my-compose-network
# In a workspace with docker-compose.yml or compose.yml, VibePod can prompt
# for a running project network interactively.
vp run claude