Mistral Vibe: Teleport Opens Up to Free Accounts
Mistral Vibe removed the internal feature gate that limited which accounts could use /teleport, its command for moving a running local session into a cloud sandbox. Sessions authenticated with a Vibe API key or a workspace API key, including free-tier accounts, can now teleport without hitting that restriction. Mistral Vibe also added a clearer error message explaining which API keys are compatible when a Codestral-only key gets rejected.
Key Takeaways
- Teleport no longer requires a gated account type, so sessions authenticated with a Vibe or workspace API key, including free accounts, can move a running session to the cloud.
- The change removes an internal feature gate rather than a documented plan restriction, suggesting the limitation was a rollout artifact rather than an intentional pricing boundary.
- Codestral-only API keys still cannot use Teleport, since the cloud sandbox needs broader model access than a Codestral key provides.
- Mistral Vibe now shows a specific error message naming which API keys are compatible when a Codestral key is rejected, instead of a generic failure.
- The fix lowers a real onboarding barrier for developers testing Mistral Vibe's cloud handoff workflow before upgrading to a paid plan.
- Teleport itself preserves session history, approvals, and diffs when a task moves from a local terminal into the cloud, so widening its availability extends that full workflow to more users.
Access Expanded to Every Tier
Mistral Vibe's /teleport command, which moves a running local CLI session into a cloud sandbox so it can keep working after a laptop closes, previously sat behind an internal feature gate that limited which accounts could use it. With the v2.25.7 release, Mistral Vibe removed that gate for sessions authenticated with a Vibe API key or a workspace API key, which means free-tier accounts can now teleport a session to the cloud without hitting an authorization wall that existed purely as an internal rollout mechanism, not a documented plan restriction.
Clearer Guidance When a Key Doesn't Qualify
Teleport still depends on having a model access path the cloud sandbox can use, and a Codestral-only API key does not qualify. Mistral Vibe added a specific, actionable error message that explains exactly which API keys will work when a Codestral key gets rejected, replacing what used to be a more opaque failure. Together the two changes make Teleport's eligibility rules both broader in practice and easier to understand when a session still cannot make the jump to the cloud.
Why It Matters
Teleport is one of Mistral Vibe's more distinctive workflow features: start a long-running refactor in the terminal, hand it off to the cloud, and come back later to a finished pull request with the full audit trail, approvals, and diffs intact. Restricting it to certain account types blunted its usefulness for anyone testing Mistral Vibe on a free plan. Opening it up removes a meaningful onboarding friction point for developers evaluating the tool before committing to a paid tier.