Choose CLI, VS Code, or web sessions
One agent, three surfaces. Vibe Code runs as the CLI, the VS Code extension, and Vibe Code Web. They share the same engine, configuration, and customization layer (agents, skills, MCP servers), so you can pick whichever fits the task at hand.
Vibe also implements the Agent Client Protocol (ACP) and is published in the ACP registry, so it can plug into other ACP-compatible clients. This page focuses on the Mistral-supported surfaces.
Get started
Pick the CLI when you want Vibe directly in your terminal.
The CLI is the most flexible surface. It runs in any terminal emulator, supports interactive sessions and scripting, and has full access to your shell and working tree.
Typical tasks:
- "Refactor
src/api/handlers/to use the new error handler pattern." - "Explain how authentication works in this repo."
- "Run the test suite, fix what fails, and commit the result."
- Scripted or unattended runs with
vibe --promptfor CI and automation.
CLI and VS Code extension share the same configuration and sessions (agents, skills, MCP servers, profiles, and conversation history). You can start a session in the CLI and resume it in the extension, or the other way around, without losing context.
To hand off work to Vibe Code Web, use the /teleport command from the CLI. See the dedicated article for the current flow and limits.
What each surface gives you
| CLI | VS Code extension | Vibe Code Web | |
|---|---|---|---|
| Local install | Required | Required | None |
| Repository access | Local clone | Local clone | Directly via GitHub |
| Filesystem and shell access | Local working tree | Local working tree, through ACP | Remote sandbox |
| Custom agents, skills, MCP servers, and connectors | Yes | Yes | Yes |
| Non-interactive mode | Yes (vibe --prompt) | No | No |
| Session lifetime | Local terminal (shared with VS Code) | Local VS Code (shared with CLI) | Managed cloud |
| Best fit | Terminal-first development, automation, CI | Editor-native development and visual review | Remote repository tasks without local setup |