Agent Architecture

Mistral Vibe

Mistral Vibe is Mistral's open-source CLI coding assistant with interactive chat, file and shell tools, todo tracking, user questions, subagent delegation, project-aware context, skills, custom slash commands, MCP server configuration, config.toml, ACP editor support, and notifications.

Source reviewed #42Checked 2026-09-07

Setup guide Source

Run type

CLI

Adapter

mcp-only

Source

OSS · mistralai/mistral-vibe

Stars

★ 5k

Archive Context

This page is one host entry inside the full architecture archive and keeps multi-surface products visible instead of collapsing them into a single run type.

42 host archive

Host page

mistral-vibe

Run cohort

CLI: 30

Archive route

/agents

Host Surface Perspectives

The host is the primary architecture boundary. Each runnable surface below separates what the host owns from what agent-connector can safely install for Mistral Vibe.

1 surface entry

CLI

cli

Host entry: A terminal command owns the process, current working directory, stdin/stdout, shell environment, and project file discovery.
Host owns: The CLI host owns agent loop timing, approval prompts, tool execution, session files, and how hook or MCP subprocesses are launched.
Connector role: agent-connector can only write the host's documented CLI config, prompt, memory, hook, MCP, or package files and point them at the home binary. Current wired connector surfaces: MCP server.
Implementation consequence: A CLI surface is byte-addressable and smoke-testable from a temporary HOME, but terminal UI behavior still belongs to the host process. No visible host-native gap is currently tracked for this surface.

Verified Architecture

Source-checked on 2026-09-07. These notes are intentionally separate from the generated surface matrix below.

Sequence #42

Source pass

Current source review findings are kept as the first architecture section so readers can separate external evidence from the generated local coverage model.

Mistral Vibe is an open-source CLI coding assistant with file editing, shell execution, search, todo tracking, interactive questions, and task delegation.
It includes built-in agent profiles, subagents, trusted folder configuration, programmatic mode, and skills-backed custom slash commands.
MCP configuration is byte-confirmed as a TOML [[mcp_servers]] array of tables with a required name alias; the only hook surface is experimental and unstable, so the row stays mcp-only by evidence rather than by omission.

Runtime boundary

The adapter target is the Vibe CLI process. Vibe owns Python packaging, interactive chat, terminal state, project scanning, Git status context, approval prompts, config home, and ACP-facing editor integrations.

The README calls Vibe Mistral's open-source CLI coding assistant.
It officially targets UNIX environments while also working on Windows.

MCP registration

MCP servers are a TOML array of tables, [[mcp_servers]], in <project>/.vibe/config.toml (project, takes precedence) or ~/.vibe/config.toml (user). Each entry carries a required short-alias name, which the adapter sets to the connector id and keys ownership on, plus transport (stdio, http, or streamable-http) with command/args/env or url/headers/api_key_env.

This is not Codex's table-keyed [mcp_servers.<name>] shape, even though both are TOML.
TOML has no interpolation, so environment references resolve to literals at install time; remote transports are registered but never telemetry-wrapped.

Hook bridge

Mistral Vibe is mcp-only in the connector matrix. The host ships only an experimental, unstable hook surface with no byte-confirmed format or event-name contract, so agent-connector wires no hooks and keeps the capability flags unset. When a first-party contract is confirmed this becomes a normal capability addition.

Tool execution approval is a safety prompt, not a hook event.
Subagent delegation through `task` is host behavior separate from hooks.

Content surfaces

Vibe content surfaces include custom system prompts, custom agent configurations, skills, custom slash commands via skills, tools, prompts, logs, session data, and multimodal file attachments.

Built-in tools include read/write/edit, bash, grep, todo management, questions, and task delegation.
ACP lets compatible editors and IDEs use Vibe.

Marketplace and host-only affordances

The host-only affordance is a Mistral-owned open-source CLI with project-aware context, approvals, notifications, ACP editor support, and configurable model/tool behavior through simple files.

Telemetry and crash reporting can be disabled in config.
Update checks query PyPI at most once per day during a session.

Host-specific shape

Mistral Vibe is an mcp-only host with TOML array-of-tables MCP configuration; experimental hooks and content surfaces are not promoted without a stable contract.

Form factor: CLI.
Native surfaces: MCP server.
Wired surfaces: MCP server.
Visible gaps: none.

Hooks

No user-installable lifecycle hook boundary is confirmed for this host.

MCP

The adapter writes this host's native MCP registration dialect, including its root key, scope, transport fields, and environment syntax.

Memory

No byte-confirmed memory/rules surface is tracked, so the adapter avoids writing managed context into an inferred file.

Marketplace and affordances

Current install is a direct native-file write path; any package artifact is manual unless a driver is added.

Runtime handlers: none.
User-visible affordances: Users see the installed connector through host-exposed MCP tools; no separate prompt, memory, or action files are wired..

Known Limits

MCP support should remain Vibe-config specific.
The experimental hook surface is a coverage ceiling, not a promised gap; do not treat approvals or questions as lifecycle hook support.
Windows support exists but UNIX is the officially targeted environment.

Evidence checked

Mistral Vibe repository Mistral AI

Architecture Diagram

Host-specific flow for the CLI surface.

mcp-only

1
Entry point: CLI
Terminal agent process reads user/project config and invokes the connector home binary for runtime callbacks.
2
Connector package
defineConnector package declares server, hooks, content, memory, and actions.
3
Adapter module: mistral-vibe
mcp-only renderer at src/adapters/mistral-vibe/index.ts.
4
Native host artifacts
Adapter writes MCP config through this host's native file, package, or marketplace surface.
5
Runtime boundary
host calls MCP tools through its client
6
User-visible surface
Users see the installed connector through host-exposed MCP tools; no separate prompt, memory, or action files are wired.
7
Coverage ceiling
1/1 native surfaces wired. No visible host-native gap in the current coverage matrix.

Component Diagram

Static parts of the Mistral Vibe integration and which side owns each one.

Mistral Vibe host
CLI surface owns the model loop, UI shell, config discovery, and native lifecycle for this integration.
agent-connector package
Normalizes connector declarations into MCP, hook, memory, content, and action payloads before delegating to a host adapter.
mistral-vibe adapter
Implements the mcp-only translation layer in src/adapters/mistral-vibe/index.ts.
Native artifacts
Adapter writes MCP config through this host's native file, package, or marketplace surface.
Runtime bridge
host calls MCP tools through its client
User-visible surface
Users see the installed connector through host-exposed MCP tools; no separate prompt, memory, or action files are wired.

Runtime Sequence Flow

Message order from install to runtime for the CLI surface.

1 · User / project
Choose host adapter
Install or update starts against Mistral Vibe; the selected surface is CLI.
2 · agent-connector
Resolve connector declaration
The package reads connector metadata and routes it to the mistral-vibe adapter instead of exposing a generic host contract.
3 · mistral-vibe adapter
Render host-native shape
Adapter writes MCP config through this host's native file, package, or marketplace surface.
4 · Mistral Vibe
Host loads artifacts
host calls MCP tools through its client
5 · Agent runtime
Run through host boundary
Users see the installed connector through host-exposed MCP tools; no separate prompt, memory, or action files are wired.
6 · Coverage matrix
Expose remaining ceiling
1/1 native surfaces wired. No visible host-native gap in the current coverage matrix.

Architecture Archive

The same five study axes are rendered for every host: runtime shape, hooks, MCP, memory, and host-only affordances.

Host-specific shape

Mistral Vibe is an mcp-only host with TOML array-of-tables MCP configuration; experimental hooks and content surfaces are not promoted without a stable contract.

Form factor: CLI.
Native surfaces: MCP server.
Wired surfaces: MCP server.
Visible gaps: none.

Hooks

No user-installable lifecycle hook boundary is confirmed for this host.

MCP

The adapter writes this host's native MCP registration dialect, including its root key, scope, transport fields, and environment syntax.

Memory

No byte-confirmed memory/rules surface is tracked, so the adapter avoids writing managed context into an inferred file.

Marketplace and affordances

Current install is a direct native-file write path; any package artifact is manual unless a driver is added.

Runtime handlers: none.
User-visible affordances: Users see the installed connector through host-exposed MCP tools; no separate prompt, memory, or action files are wired..

Special Feature Inventory

Host-specific capabilities separated from the generic surface matrix: lifecycle hooks, MCP registration, memory/rules, marketplace delivery, and UI or content affordances owned by the host.

Lifecycle hooks

Not confirmed

No user-installable lifecycle hook boundary is confirmed for this host.

MCP registration

Wired

The adapter writes this host's native MCP registration dialect, including its root key, scope, transport fields, and environment syntax.

Memory and rules

Not confirmed

No byte-confirmed memory/rules surface is tracked, so the adapter avoids writing managed context into an inferred file.

Marketplace delivery

Direct files

Current install is a direct native-file write path; any package artifact is manual unless a driver is added.

Host-only affordances

Not confirmed

Wired host affordances: none. Host-native gaps: none. Not confirmed: Commands, Skills, Subagents, Statusline handler, Action affordances.

Source Review Notes

Latest source pass for host-specific architecture details. This is separate from generated adapter coverage and local drift guards.

Checked 2026-09-07Open review source

mistralai/mistral-vibe repository

Mistral Vibe is an open-source CLI coding assistant with file editing, shell execution, search, todo tracking, interactive questions, and task delegation.
It includes built-in agent profiles, subagents, trusted folder configuration, programmatic mode, and skills-backed custom slash commands.
MCP configuration is byte-confirmed as a TOML [[mcp_servers]] array of tables with a required name alias; the only hook surface is experimental and unstable, so the row stays mcp-only by evidence rather than by omission.

Evidence Map

Each host page ties public source evidence to the local adapter and drift guards that keep the rendered archive aligned with code.

Public source: mistralai/mistral-vibe

Primary public repository or product source used for current host status and source links.

external

Open source

Local adapter implementation

Defines the install/uninstall behavior, native config rendering, capability flags, and any runtime parse/format bridge for this host.

local

src/adapters/mistral-vibe/index.ts

Platform metadata and host-native matrix

Records the form factor, public source target, ranking source, native host surfaces, and current agent-connector coverage cells.

local

site/src/platform-data.ts

Architecture drift guard

Asserts that every registered host has a page, diagram, host-specific brief, source link, form-factor band, and adapter-aligned surface data.

local

tests/docs/platform-drift.test.ts

Runtime Shape

The host accepts MCP registration, but has no confirmed hook bridge for agent-connector to call.

MCP registration: Wired through this adapter
Hook bridge: No confirmed hook surface

Connector Surfaces

Static content

MCP server

Runtime handlers

No runtime handler surfaces wired

Surface Matrix

Wired means agent-connector installs it now. Host native marks support we know about but have not wired yet.

SurfaceStatus

MCP server

Static content

agent-connector installs this surface today.

Wired

Hooks

Static content