Deployment View

Infrastructure Level 1

deploy level1
Motivation

Vibe is a client-side tool. The only "deployment" is the package installed on the developer’s machine; there is no server component owned by this bounded context. All server-side systems are external ([section-context-and-scope]).

Quality and/or Performance Features

The process is single-user and single-process. State lives under ~/.vibe/ (overridable with VIBE_HOME): config.toml, .env, session logs, the trust list, plans and the update cache [vibe/core/paths/_vibe_home.py:19-36].

Mapping of Building Blocks to Infrastructure

All nine building blocks run inside the single vibe/ (or vibe-acp) process on the developer machine. The Remote block additionally talks to the Vibe Code / Nuage cloud.

Infrastructure Level 2 — Distribution channels

Channel Evidence

PyPI package mistral-vibe, installed via uv tool install or pip

README.md:45-55, pyproject.toml:143-144

One-line scripts/install.sh (Linux / macOS)

README.md:27-33

Standalone binary built with PyInstaller

vibe-acp.spec, pyinstaller/runtime_hook_truststore.py, .github/workflows/build-and-upload.yml

Packaged GitHub Action (uv sync + uv run vibe/ -p)

action.yml:1-60

Zed editor extension

distribution/zed/extension.toml

Releases are cut by the .github/workflows/release.yml workflow; CI runs in .github/workflows/ci.yml [.github/workflows/].