- AI_PATH_B_EXECUTION_PLAN.md: Status changed from "proposed" to
"week 1 shipped", weeks 1-3 checkboxes flipped to ✅ for the parts
that landed in vibn-frontend@4ba9407 and @41d4d37. Lists what's
still manual (DNS wildcard, Coolify host image build, Traefik cert).
- vibn-dev/PREVIEWS.md: Architecture for *.preview.vibnai.com
routing, the deferred Coolify-compose-hot-update piece, and an
HMR/websocket troubleshooting checklist.
- vibn-dev/setup-on-coolify.sh: One-shot script to build
vibn-dev:latest on the Coolify host (referenced by the compose
template's pull_policy: never).
Made-with: Cursor
vibn-dev
Per-project AI development container. One of these runs in Coolify per
Vibn project; the AI agent (Gemini) drives it via shell.exec and
fs.* MCP tools.
See /AI_PATH_B_EXECUTION_PLAN.md for the architecture.
Build & publish
docker build -t registry.vibnai.com/vibn-dev:latest .
docker push registry.vibnai.com/vibn-dev:latest
The image is pre-pulled on every Coolify host on deploy so first-use spin-up stays under 5 seconds.
Smoke test locally
docker build -t vibn-dev .
docker run --rm -it -v "$PWD/scratch:/workspace" vibn-dev bash
# inside: mise install # pulls Node lts + Python 3.12 (~90s, one-time)
# inside: rg --version # ripgrep ships in the base image
# inside: git --version
What's NOT in the image (by design)
- Node/Python/Go/Rust toolchains — lazy-installed via mise
- Coolify control-plane creds — never. The container has no route to internal Vibn services (Docker network policy enforced at host level)
- SSH server — exec happens via
docker execfrom the Coolify host