TWITTER_ARTICLE

On 2026-03-05, Letta introduced remote environments for Letta Code, letting users…

2026-03-05 · 00:10 UTC ·Letta_AI ·1 min read

Brief

Letta’s new remote environments feature decouples the chat interface from execution, so users can message agents via chat.letta.com while those agents run on machines they register themselves. The system relies on a local WebSocket server, supports execution across laptops, ephemeral sandboxes, and remote VMs like Railway or GCP, and maintains persistent agent memory plus the same approval and autonomy controls available in the Letta Code CLI.

Why it matters

On 2026-03-05, Letta introduced remote environments for Letta Code, letting users interact through chat.letta.com while agents execute on registered machines such as a local laptop, cloud sandbox, or remote VM.

Key details

  • Letta says its agents are stateful, so a single agent can move between environments—including within the same conversation—without losing memory, conversation history, or attached context repositories.
  • Remote environments use a local WebSocket server and preserve Letta Code’s human-in-the-loop permission system, including Default, Accept Edits, Plan, and Bypass Permissions modes, with approvals surfaced in chat.letta.com for users to approve, deny, or edit tool calls.
Cleaned source text

title: @Letta_AI: We're introducing remote environments , a way to separate where you interact wit...

author: Letta_AI

content_type: twitter_article

published: 2026-03-05T00:10:43+00:00

source_url: https://x.com/Letta_AI/status/2029348848913793333

word_count: 335

We're introducing remote environments , a way to separate where you interact with a Letta agent from

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 that run locally on registered machines through chat.letta.com . For example, you can message agents running on your laptop from your phone.

Letta Code agents are stateful, so agents can move across execution environments without losing their memory and context (e.g. conversation history, context repositories , etc.)

Remote execution for agents

Any machine (whether it's your local MacBook or a cloud sandbox) can be used as a remote execution environment. To register a machine, install Letta Code and start the Letta Code server:

This will start a WebSocket server locally, and you can name your environment for easy discovery:

On chat.letta.com , you can select which remote environment your agent uses when you message your agent:

Agents that can move across machines

With remote environments in Letta Code, a single agent can work across:

Your laptop

An ephemeral sandbox

A remote VM (e.g. Railway, GCP)

Regardless of where your agent runs, it still has the same persistent memory. Agents can even move across environments in the same conversation.

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: A

uto-approve file edits, prompt for everything else

Plan: A

gent plans but doesn't execute

Bypass Permissions: F

ull autonomy, no approval prompts ("yolo-mode")

Next steps

You can register your machine as a remote environment running the WebSocket server using the latest Letta Code package:

Then, just visit chat.letta.com .

Posted: 2026-03-05T00:10:43.000Z

Engagement: 249 likes, 26 retweets, 3 replies