Context and Scope

Vibe is a client-side tool that runs on the developer’s machine. The system boundary in this chapter is the same one used in [section-building-block-view]: the building blocks there are internal to this boundary, the systems below sit outside it.

Business Context

context business

The developer states a coding goal; Vibe turns it into LLM calls and tool executions and reports the result. A scripter drives the same engine non-interactively. An integrator embeds the agent in an editor through the ACP server. The LLM Provider supplies the agent’s reasoning; Vibe Code / Nuage optionally continues a session in the cloud [vibe/core/programmatic.py:27, vibe/acp/entrypoint.py:78-108, vibe/core/teleport/teleport.py:46-150].

Technical Context

context technical
External System Channel Code Evidence

LLM Provider API

HTTPS (Mistral SDK or generic HTTP)

vibe/core/llm/backend/factory.py:1-7, vibe/core/llm/backend/mistral.py:268-335

Mistral Datalake

HTTPS POST to api.mistral.ai/v1/datalake/events

vibe/core/telemetry/send.py:30-31

GrowthBook

HTTPS POST to the eval endpoint; fails open on error

vibe/core/experiments/client.py:17-81

MCP Servers

http, streamable-http or stdio

vibe/core/tools/mcp/registry.py:80-150

Vibe Code / Nuage

HTTPS + Server-Sent Events

vibe/core/nuage/client.py:22-100, vibe/core/nuage/remote_events_source.py:33-120

GitHub

OAuth device flow; release lookups

vibe/core/auth/github.py:117-184, vibe/cli/update_notifier/adapters/github_update_gateway.py

PyPI

HTTPS version lookup, cached 24 h

vibe/cli/update_notifier/adapters/pypi_update_gateway.py, vibe/cli/update_notifier/update.py:82