Mistral Vibe: Git-Aware @ File Mentions
Mistral VibeMistral Vibe upgraded its @ file-mention autocomplete to use Git-aware discovery, surfacing tracked and non-ignored files more reliably in large repositories. The same update lets developers drop a standalone pasted file or folder into the prompt via @, not just files already indexed by the workspace scan. It shipped in v2.25.3 alongside the new /branch command.
Key Takeaways
- Git-aware discovery now drives the
@autocomplete, surfacing tracked and non-ignored files instead of every file from a directory walk. - Pasted files and folders are now accepted directly through
@, even when they aren't already part of the workspace's indexed file list. - Targets large repositories, where build output, vendored code, or generated files previously cluttered the suggestion list.
- Shipped in v2.25.3, the same release that introduced the
/branchcommand and the session-log permissions fix. - Addresses a high-frequency workflow, since
@file mentions are one of the most common ways developers steer the agent's attention. - Reduces friction between tools, letting a path copied from a terminal or file manager work as a mention without extra steps.
Git-Aware File Discovery
Mistral Vibe changed how its @ file-mention autocomplete finds candidates in version 2.25.3, switching to Git-aware discovery. Instead of relying purely on a generic directory walk, the autocomplete now leans on git's own view of a repository, tracked files and files respecting .gitignore, to decide what belongs in the suggestion list. In large repositories with generated output, build artifacts, or vendored dependencies sitting alongside source code, this keeps the @ picker focused on the files a developer is actually likely to want to reference.
Standalone Pasted Files and Folders
The same change lets @ accept a file or folder that has been pasted directly into the prompt, rather than requiring every reference to resolve against the workspace's existing file index. A developer can now paste a path from outside the immediate autocomplete flow and have Mistral Vibe pick it up as a first-class file reference, closing a gap between how people actually work, copying paths from a terminal, another tool, or a file manager, and how the mention system expected input.
Why It Matters
File mentions are one of the most frequently used ways developers steer Mistral Vibe's attention to specific code, so noise in the autocomplete list or friction when referencing a file outside the indexed set has an outsized effect on day-to-day usability. Making the picker Git-aware and letting it accept pasted paths removes two small but recurring points of friction from a workflow developers rely on constantly.