Remote Environments

Manage named Letta server connections — like git remotes for your agent infrastructure.

lettactl remote add <name> <url> [options]

Flag	Type	Description
--api-key	string	API key for authentication (required for Letta Cloud)

lettactl remote add local http://localhost:8283

lettactl remote add production https://api.letta.com --api-key sk-xxx

lettactl remote add staging https://staging.example.com --api-key sk-stg-xxx

The first remote added is auto-activated.

Remote configs are stored in ~/.lettactl/remotes.json.

Remove a named remote. If the active remote is removed, the first remaining remote becomes active.

lettactl remote remove <name>

lettactl remote remove staging

Set the active remote. All subsequent commands will target this server.

lettactl remote use <name>

lettactl remote use production

lettactl remote use staging && eval $(lettactl remote env)

The active remote is loaded automatically on every CLI invocation.

Explicit LETTA_BASE_URL environment variable always takes precedence over the active remote.

List all configured remotes. The active remote is marked with an asterisk (*).

lettactl remote list

lettactl remote list

Show details of a specific remote including URL and API key status.

lettactl remote show <name>

lettactl remote show production

Output shell export statements for the active remote. Use with eval to apply to current session.

lettactl remote env

eval $(lettactl remote env)

eval $(lettactl remote env 2>/dev/null)

Outputs to stdout for use with eval. Errors go to stderr.

Useful for CI/CD scripts that need environment variables set.