Vibe Desktop: Create Projects From Any Existing Folder
Mistral VibeMistral Vibe removed a friction point in Vibe Desktop: it can now create a local project from any existing folder, rather than requiring a specific starting state before a folder could become a project. For developers bringing an existing codebase into Desktop, this closes a gap between the CLI, which has long worked against arbitrary directories, and the desktop app's project model.
Key Takeaways
- Vibe Desktop can now create a project from any existing folder, removing a prior restriction on how projects had to be started.
- The change brings Desktop's project creation closer to the CLI, which has long worked against arbitrary existing directories.
- It directly affects onboarding for existing codebases, the most common starting point for developers adopting the tool.
- The update is listed under Changed, not Added, indicating it alters existing project-creation behavior rather than introducing a new surface.
- It's a small but high-frequency touchpoint: project creation is typically the first action a Desktop user takes.
- The change reduces friction for teams migrating existing repos into Vibe Desktop rather than starting fresh.
Closing a Gap Between CLI and Desktop
Vibe Desktop organizes work around projects, and up to this release, turning an arbitrary existing folder into a Desktop project came with more friction than the CLI equivalent, where developers can simply run vibe inside any directory. With v2.25.1, Mistral Vibe changed that: Vibe Desktop can now create a local project from any existing folder directly, without extra setup steps standing between a developer's existing code and Desktop's project view.
Why It Matters for Everyday Use
Most developers adopting an agentic coding tool are not starting from a blank folder, they're bringing an existing repository or project they already work in daily. A desktop app that makes that path smooth, rather than nudging developers toward greenfield scaffolding, removes a real first-impression obstacle. The change is a small one in the changelog, but it directly affects the very first thing a new or returning Desktop user does: pointing the app at the code they actually want to work on.