Deploy a Letta Code remote environment to any cloud platform. Runs letta server so your agent is always-on and accessible from chat.letta.com or the Letta Code desktop app.
letta server opens an outbound WebSocket to Letta Cloud. No inbound ports, no reverse proxy, no domain name needed.
On first deploy, letta server starts an OAuth device flow and prints an authorization URL in the logs. Open the URL, approve the request, and the server connects. Auth tokens are persisted under ~/.letta/, so container deployments need a persistent volume mounted at /root to survive restarts.
OAuth is the only authentication method on Pro, Max-lite, and Max plans. On Developer plans, you can alternatively set LETTA_API_KEY as an environment variable to skip OAuth.
If you set LETTA_BASE_URL to a self-hosted server, device flow is not available. Use LETTA_API_KEY.
cp .env.example .env
docker compose up -d
docker compose logs -f
# Check the logs for the OAuth URL and approve it in your browserThe included docker-compose.yml mounts letta-data at /root, so auth survives container restarts.
SSH into a $4/mo droplet and run directly:
curl -fsSL https://deb.nodesource.com/setup_20.x | bash -
apt-get install -y nodejs python3 make g++
npm install -g @letta-ai/letta-code
letta server --env-name "cloud"
# Check the output for the OAuth URL and approve it in your browserOr use Docker:
apt-get install -y docker.io docker-compose-v2
git clone https://github.com/letta-ai/letta-code-server-deployment.git
cd letta-code-server-deployment
cp .env.example .env
docker compose up -d
docker compose logs -f
# Check the logs for the OAuth URL and approve it in your browserIf you bootstrap with OAuth over SSH, the saved auth state under /root/.letta is reused across restarts.
fly launch --name letta-remote --no-deploy
fly volumes create letta_data --region sjc --size 1
fly deploy
fly logs --app letta-remote
# Check the logs for the OAuth URL and approve it in your browserThe included fly.toml mounts /root, so auth survives machine restarts.
Use the Deploy on Railway button at the top of this README. The template includes a persistent volume mounted at /root.
After deployment, open the deploy logs, find the OAuth URL, and approve it in your browser.
For deployments that should automatically pick up new Letta Code releases, connect the service to this GitHub repo instead of leaving it as a pinned template snapshot:
- Repository:
letta-ai/letta-code-server-deployment - Branch:
main - Root directory:
/ - Builder: Dockerfile
- Volume mount:
/root - Automatic deploys: enabled
This repo commits a letta-code-version.txt bump whenever a new @letta-ai/letta-code npm release ships. Railway then sees a normal Git commit and redeploys services connected to main.
Or via CLI:
railway init
railway up
railway logs
# Check the logs for the OAuth URL and approve it in your browserThis repo tracks the Letta Code npm release in letta-code-version.txt. A scheduled GitHub Actions workflow checks @letta-ai/letta-code and commits a version bump to main when a new release ships.
That gives Railway a real Git commit to deploy. Any Railway service connected to this repo with automatic deploys enabled will rebuild and install the new Letta Code version without manual redeploys.
Other platforms still update on rebuild:
- Railway template snapshots: reconnect the service to
letta-ai/letta-code-server-deploymenton branchmain, then enable automatic deploys. - Fly:
fly deploy. - Docker Compose:
docker compose build --pull && docker compose up -d.
To pin a specific version, set the Docker build arg LETTA_CODE_VERSION=<version> or fork this repo and edit letta-code-version.txt.
To connect your remote agent to Telegram or Slack:
- Open the Letta Code desktop app.
- Switch to your remote server in the device picker (bottom left).
- Open the Channels sidebar and add a Telegram bot or Slack app.
Configuration, pairing, and binding all happen through the app's WebSocket control channel — no shell access or env vars needed on the server.
Enabled channel adapters are restored automatically after container restarts. You should not need to edit the Railway start command or add --channels telegram manually.
| Variable | Default | Description |
|---|---|---|
LETTA_API_KEY |
optional | Your Letta API key from app.letta.com. Developer plans only. If unset, the server uses OAuth device flow. Required for self-hosted deployments. |
ENV_NAME |
cloud |
Name shown in the environment picker on chat.letta.com |
LETTA_RESTORE_ENABLED_CHANNELS |
1 |
Restores enabled channel adapters from the persistent volume when the server starts. Keep this enabled for Telegram and Slack remotes. |
LETTA_BASE_URL |
https://api.letta.com |
Override for self-hosted Letta servers. |
- Deploy using any method above
- Open chat.letta.com or the Letta Code desktop app
- Select your remote environment from the picker (bottom left)
- Send a message