| name | teleporting-between-environments |
| description | Moves the current agent conversation to Cloud or a Cloud-registered remote environment while coordinating machine-local files and setup. Use when the user says "let's continue this task on cloud", asks to continue or move work on another connected computer, wants to teleport between environments, or needs to upload or download artifacts before a handoff. |
Teleporting Between Environments
Teleport the current agent and conversation without losing conversational memory. Prepare machine-local state first, then let the destination continue the same task.
Mental model
- Memory follows the agent; filesystem access does not. Files, working directories, credentials, running processes, and local services belong to the computer currently executing the conversation.
- Upload and download paths are relative to the current computer. Cloud cannot read a laptop path until the conversation teleports to that laptop.
- The conversation’s managed Cloud sandbox remains alive while the conversation runs elsewhere.
- Filesystem paths and cwd do not transfer between computers. Re-establish the destination’s repository, working directory, dependencies, credentials, and services after arrival.
Commands
letta teleport list
letta teleport cloud
letta teleport <environment>
list: show accessible online remote targets. Desktop Local is excluded.cloud: create or resume this conversation’s managed Cloud sandbox.<environment>: target a listed remote environment by its friendly selector.
Teleport cannot target Desktop Local yet. Once the conversation runs in Cloud,
the agent cannot programmatically return to Desktop Local. The user can still
switch manually with Desktop's environment picker. Do not run or recommend
letta teleport back.
Transfer files with the existing sandbox commands:
