Skip to main content

Environment variable migration

Every variable AgentArea reads is now AGENTAREA_<DOMAIN>_<KEY>. The old names are not accepted: there is no alias and no fallback, so a stale name is ignored rather than silently honoured. Update .env and your Helm values in one pass before upgrading — see Configuration for the scheme itself. Three shapes of change appear below:
  • Renamed — same value, new name. Most rows.
  • Merged — two old names collapsed onto one new name, because they always carried the same value. ACTIVATION_PORT and AGENTAREA_EVENTS_PORT both become PORT.
  • Retyped — durations now carry their unit in the value. TTL, TIMEOUT, INTERVAL and GRACE variables take 30s, 5m, 2h; a bare number is rejected. AGENTAREA_SANDBOX_MAX_EXEC_SECONDS and AGENTAREA_SANDBOX_EXEC_SECONDS are the exceptions and still take plain integer seconds.
Names left unprefixed belong to a third party — the postgres image, the AWS SDK, OpenTelemetry, the Ory SDK, the Next.js build, and the PORT/HOST pair the platform injects. Those are unchanged. Two of our settings moved onto such a contract instead of getting a prefix: the Temporal connection is TEMPORAL_ADDRESS / TEMPORAL_NAMESPACE (plus TEMPORAL_API_KEY and TEMPORAL_TLS_* when needed), which the Temporal SDK reads itself, and the execution cluster is the standard KUBECONFIG.

Removed

These were read by nothing, or were a second way to say something already configured. Delete them; there is no replacement.

Renamed

Database

Object storage

Authentication

Authorization

Secret manager

MCP

Sandbox

Temporal

Tasks

Triggers

Channel delivery

Event service

CORS

Metrics

Logging

Redis

Kubernetes backend

Application

Listen address

Last modified on October 4, 2026