Teleport from CLI to web

Teleport moves a CLI session into a Vibe Code Web sandbox so the task can keep running without your terminal staying open. Use it when a task is long, when you want to follow it from another device, or when you want the agent to push commits and open a pull request from the cloud.

Information

Teleport is part of the Vibe Code Web sandbox flow, currently in Public Preview. Capabilities, limits, and the interface can change before general availability.

Prerequisites

Before you teleport, make sure that:

You use an API key tied to a Pro, Team, or Enterprise account.
The Mistral GitHub App is installed on the repository you're working in.
Your session uses a model served by the Mistral API, such as Mistral Medium 3.5. Sessions on other providers or local servers, including self-hosted Devstral, can't be teleported. Run /model to switch first.
You run the CLI from a Git repository with a GitHub remote, with a branch checked out (not a detached HEAD).

Update to the latest CLI before you start:

vibe update

vibe update

Two ways to use Teleport

Send a single prompt to a cloud session

From inside a Git repository, prefix any prompt with &:

vibe
> & fix the failing tests

vibe
> & fix the failing tests

The task runs in a cloud sandbox. The CLI returns a Vibe Code Web URL where you can follow the session.

Move an in-progress local session to the cloud

Inside an active local session, run:

/teleport

/teleport

Vibe summarizes the conversation, then starts a Vibe Code Web session from your current branch and commit, including uncommitted changes. The CLI prints the session URL, which you can follow from any device signed in to Vibe.

The first time you teleport from a repository, Vibe asks you to pick the Vibe Code Web project to use and remembers it. Run /remote-project to change it. If your branch isn't on the remote or has unpushed commits, Vibe asks before pushing, and cancels the teleport if you decline.

What happens after Teleport

When the cloud session runs, the agent typically:

Clones your repository into the sandbox.
Works through the task: reads files, runs commands, edits code.
Streams progress into Vibe Code Web in real time.
Asks clarifying questions when needed.
Pushes a branch and opens a draft pull request when done.

Commits, branches, and pull requests created during the run stay in your repository. The sandbox is deleted when the session ends.

Limits

Limit	Value
Maximum session duration	24 hours
Inactivity timeout (waiting for your reply)	3 hours
Individual command timeout	30 seconds
Concurrent sessions per user	Plan-dependent

Known caveats

Teleport is one-way. Once a session moves to the cloud, you can't pull it back into the local CLI. Continue from Vibe Code Web.
Only works from a GitHub repository with a checked-out branch. Running it from another directory fails.
Cloud sessions run on Mistral Medium 3.5, regardless of the local model.