Mistral Vibe: Multi-Repository Sessions with --add-dir
Mistral VibeMistral Vibe v2.10.0 introduces the --add-dir flag, enabling developers to pull additional repository roots into a single agent session at startup. This makes it straightforward to work across multiple codebases — a frontend and backend repo, a main application alongside a shared library, or application code with infrastructure configuration — without spinning up separate sessions. The same release also promotes Mistral Vibe's connector integrations to public GA endpoints, marking their first production-grade availability following the beta rollout in April 2026.
Sources & Mentions
3 external resources covering this update
--add-dir: True Multi-Repository Context in a Single Session
One of the persistent limitations of CLI coding agents is their scope: a session typically anchors to a single working directory, creating friction when a task spans multiple repositories. Mistral Vibe v2.10.0 addresses this directly with the --add-dir flag.
How It Works
The --add-dir flag accepts one or more additional directory paths at session startup, pulling those repository roots into the agent's active context alongside the primary working directory. A typical invocation looks like:
vibe --add-dir ../shared-library --add-dir ../infra
This allows the agent to read, navigate, and reason about files across all specified repositories within a single conversation. The flag is particularly useful for:
- Fullstack projects where the frontend and backend live in separate repos but share interfaces, types, or API contracts
- Monorepo-adjacent setups where a main application depends on a sibling library or tooling repo
- Infrastructure-as-code workflows that require coordinating application code and deployment configuration simultaneously
Previously, working across these boundaries meant either copying context manually into prompts or maintaining parallel agent sessions — an ergonomic burden that --add-dir eliminates.
Connectors Reach General Availability
The v2.10.0 release also promotes Mistral Vibe's connector integrations to public GA endpoints. Connectors — which link the Vibe agent to external services like GitHub, Linear, Jira, Sentry, Slack, and Teams as part of the remote agents feature — are now available at stable, production-grade URLs. The accompanying enable_connectors config flag gives administrators explicit control over whether connector features are available in a given environment.
This is the first classification of connector functionality as fully production-ready, following the beta rollout initiated with the remote agents launch in April 2026.
Bug Fixes Relevant to Users
The release also resolves a regression where slash commands broke when automatic IDE context was enabled — a notable fix for users who rely on custom slash-command skills within IDE-integrated Mistral Vibe workflows.