Remote Environments for Letta Code

We're introducing Remote Environments, a way to separate where you interact with a Letta agent from where it executes. Using remote environments, you can interact with Letta agents from chat.letta.com that run locally on registered machines - meaning you can message an agent working on your laptop from your phone.
The same agent can even move between remote environments within a conversation, allowing agents to work across machines just like a human developer. When an agent moves between execution environments, all its memory (e.g. conversation history, context repositories, etc.) come with it. You can continue a conversation on a remote sandbox on your local machine, and the agent will still have the same persistent memory and conversation history. You can see more about how Letta agent’s memory work with our latest blog post on context repositories.
Remote execution for agents
Running letta server on any machine starts a WebSocket server and registers it as a named execution environment for your agent:

On chat.letta.com, you can select which remote environment to run your agent on.
Agents that can move across machines
Most agents today are defined by their environment: memories, skills, files, and other context are stored locally and must be explicitly transported. In contrast, human developers move between environments without losing context.
In Letta Code, all sessions are tied to a persistent agent that has an identity and associated memory. With remote environments in Letta Code, a single agent can work across:
- Your laptop
- An ephemeral sandbox
- A remote VM (e.g. Railway, GCP)
Permission modes when working remotely
Remote Environments carry the full human-in-the-loop approval flow over WebSocket. When the agent invokes a tool that requires approval, the approval request is surfaced in chat.letta.com. The user can approve, deny, or edit the tool arguments before execution proceeds.
You can configure the same permission modes with remote execution as you can with the Letta Code CLI:
- Default — standard approval checks for sensitive operations
- Accept Edits — auto-approve file edits, prompt for everything else
- Plan — agent plans but doesn't execute
- Bypass Permissions — full autonomy, no approval prompts
Next steps
You can register your machine as a remote environment by running letta server after updating to the latest version.
Install Letta Code with npm install -g @letta-ai/letta-code






















.png)






