Environment Variables Reference

Overview

Environment variables control how your OpenClaw instance connects to services and configures its runtime behavior. Most variables are set automatically by ClawHosters based on your dashboard settings. Some can be customized via SSH for advanced use cases.

Variables Set by ClawHosters

These variables are managed automatically. Changing your dashboard settings updates them on the next config deployment.

Instance Identification

LLM Configuration

LLM_MODE values:

When LLM_MODE is managed, the proxy URL is also set:

Playwright (Browser)

This is set in all instances. Chromium is pre-installed in the base snapshot for web automation skills.

Docker Compose Variables

These variables are set in the docker-compose.yml file and affect the container runtime:

The NODE_OPTIONS variable limits the Node.js heap size to prevent the container from running out of memory. It is set based on your tier's Docker memory limit.

Viewing Current Variables

Via Dashboard

Your instance's current environment variables are visible in the instance detail page. Sensitive values (API keys, tokens) are masked.

Via SSH

To see all variables inside the running container:

docker exec openclaw-<id> env

To check a specific variable:

docker exec openclaw-<id> printenv LLM_MODE

Adding Custom Variables

If you need to set custom environment variables (for MCP servers or custom skills):

Temporary (Until Container Restart)

docker exec openclaw-<id> bash -c "export MY_VAR=value && ..."

This does not persist across restarts.

Persistent (Via .env File)

SSH into your instance and edit the .env file:

# On the host (not inside the container)
nano /opt/openclaw/.env

Add your variable:

MY_CUSTOM_VAR=some-value

Then restart the container:

cd /opt/openclaw && docker compose restart

Custom variables in .env persist across restarts but are overwritten during a full redeploy from the dashboard. To keep custom variables after redeploy, add them again after each deployment.

Security Notes

• API keys are stored encrypted in the ClawHosters database
• Keys are decrypted only during config deployment
• On the instance, keys exist as plaintext in openclaw.json and environment variables
• The instance's firewall restricts network access, limiting exposure
• Never share your instance's .env file or openclaw.json — they contain secrets

Related Documentation

• OpenClaw Configuration Reference — Config file structure
• Docker Configuration — Container settings
• Resource Limits — Memory limits by tier
• SSH Access — Connecting to your instance