Back to rankings

Mistral Vibe: Teleport and Project Links in VS Code

Mistral VibeView original changelog

Mistral Vibe 2.26.0 brought project links and teleport to its VS Code extension. Users can link a local workspace to a Vibe Code Web project and teleport the current conversation to continue it in the browser.

Key Takeaways

  • The VS Code extension can now link a local workspace to a Vibe Code Web project.
  • Teleport sends the current conversation to the browser to continue there.
  • Editor users no longer need a terminal to hand off a session.
  • The Rust CLI gains matching /teleport, &<prompt> and --teleport entry points with push approval.
  • Teleport now resolves git at the session workspace, fixing false 'requires a git repository' errors.
  • A 'Failed to summarize context' failure with thinking models on the experimental harness is fixed.

Moving a session from the editor to the browser

The Mistral Vibe VS Code extension gained two connected features in 2.26.0. Project links let a user tie a local workspace to a Vibe Code Web project. Teleport then sends the current conversation to that project so work can continue in the browser, for example when moving from a laptop to a different device or handing a long task to a hosted environment.

Why it matters

Teleport already existed in the CLI, and the same release extends it in other places: the Rust CLI gains /teleport, &<prompt> and --teleport, with push approval and Esc to cancel. Bringing project links and teleport to VS Code means editor users no longer have to switch to a terminal to hand a session off.

Related fixes

Teleport now resolves git at the session's workspace instead of the agent process's working directory, which fixes "requires a git repository" errors on eligible projects. It also no longer fails with "Failed to summarize context" on the experimental harness when the model uses thinking.