Runtime Configuration

This page lists runtime and operator environment variables. For agent authoring, use the Declarative Reference; it is the single source for every accepted agent.md field, default, profile, and exception. Provider credentials are grouped in Adapters, and deployment behavior is covered in Runtime And Deployment.

Committed Production Configuration

agent/config.production.ts holds shared non-secret runtime values:

import { defineProductionConfig } from "@assemblyline-agents/core";

export default defineProductionConfig({
  SEARCH_API_URL: "https://search.example.com/v1",
  ASSEMBLY_LINE_MAX_CONCURRENT_RUNS: "16"
});

The default export must be one inline defineProductionConfig({...}) call. Keys use uppercase environment syntax and values are string literals. The compiler rejects dynamic code and secret-like fields or values, then serializes the map into manifest.json. Local shell/host values override committed values; framework defaults apply only when neither is set. .env is not loaded.

Configuration may be contextual. Credentials are capability-scoped. API URLs, regions, limits, and feature switches belong here. Passwords, tokens, private keys, connection strings, and authenticated webhook URLs belong in the configured secret store; bootstrap and deploy credentials remain host secrets.

Environment Variable Reference

Every ASSEMBLY_LINE_* variable read by the packages in this repo. Boolean variables accept true/1 and false/0 unless noted. Provider-specific non-ASSEMBLY_LINE_ env (API keys, DATABASE_URL, SLACK_*, ...) is documented in Adapters and Runtime And Deployment.

Alphabetical index

Every variable in this reference, with the section that documents it. ASSEMBLY_LINE_ARTIFACT_ROOT, ASSEMBLY_LINE_AGENT_REVISION, and ASSEMBLY_LINE_MIGRATION_FILES are deploy-time outputs, not knobs; see Build, deploy, and migrations.

Server and auth (@assemblyline-agents/node)

Usage accounting

Usage accounting is observational: it does not reserve quota, reject requests, or estimate missing token/cash values. Provider transactions are stored in exact integer micro-dollars when the provider reports cash; otherwise cash is null with unavailable provenance. control_total rows are provider aggregate evidence and are excluded from the default transaction view so they cannot double count run receipts.

Concurrency and rate limiting

Graceful shutdown

OTLP telemetry (@assemblyline-agents/otlp)

Durability workers and recovery

Delivery queue

For sandbox-backed turns, only deliver_artifact selections are attached. A response containing sandbox:/workspace/... links does not select a file. With no selection, no workspace files are attached. Internal cache and tool byproduct paths are never eligible. The count and byte settings limit the selected attachment set; exceeding either limit fails delivery preparation instead of silently omitting a requested file. deliver_artifact stores the selected bytes as a private content-addressed blob before recording the durable selection. Final delivery therefore reads only immutable selection metadata and does not wait for a recursive workspace scan or asynchronous workspace sync.

Sandbox sync and hydration

Versioned workspaces

Workspace retention keeps the head, named checkpoints, fork sources, and a bounded automatic tail. The operator CLI uses authenticated deployed-agent routes:

Committed search uses Postgres full-text ranking. Optional semantic search uses the root model plugin's declared embedding implementation and optional Postgres migration 021_assembly_line_workspace_embeddings_pgvector. Without it, search remains full-text with deterministic direct-content fallback for stale indexes.

Sandbox snapshots

Model loop, memory, and logging

Attachments and resource projection

Provider channel modules own authenticated attachment resolution. If a channel resolver declines an attachment, the runtime preserves metadata only; it does not fetch a fallback URL. Direct runtime.run() callers must set allowRemoteAttachments: true for a generic public HTTP(S) download. Every download resolves and rejects private/special-use addresses, revalidates each redirect, strips credentials on cross-origin redirects, applies byte/time limits, and bounds ZIP inflation to declared and configured quotas. Ordinary links in message text are unaffected.

Self-improvement, dynamic automations, dynamic connections

Runtime environment overrides for the resolved mutability policies.

Scheduler

Secrets and local store paths (@assemblyline-agents/node)

Build, deploy, and migrations (CLI and compiler)

Built-in deploy options use the same precedence everywhere: CLI flag, environment variable, resolved gateway profile option, then provider default. A hosted plan warns when local state or local blob storage is selected because those files may disappear when a container is replaced.

During a hosted deploy the CLI sets these in the migration process environment (they are outputs, not knobs): ASSEMBLY_LINE_ARTIFACT_ROOT, ASSEMBLY_LINE_AGENT_REVISION, ASSEMBLY_LINE_DEPLOY_ENV, ASSEMBLY_LINE_MIGRATION_FILES.

Provider: Postgres (@assemblyline-agents/postgres)

The neon, railway, and supabase state profiles all read DATABASE_URL by default and use the same Assembly Line schema and migrations. The railway profile additionally accepts databaseService (default Postgres) and provision (default true). During a Railway deploy, those options create or reuse that Railway database service and wire a private DATABASE_URL reference onto the application service. Named non-default services must already exist and use provision: false. The preset also defaults sslRejectUnauthorized to false for Railway's generated Postgres certificate; TLS remains enabled. For Supabase, use the direct URL on an IPv6-capable persistent host or the session-pooler URL when IPv4 is required.

Provider: Docker (@assemblyline-agents/docker)

Provider: Hetzner VPS (@assemblyline-agents/vps)

Supported.

The deploy.hetzner options are:

Each host inventory entry requires ingress: { baseDomain, defaultVisibility }. Create one wildcard DNS record for *.<baseDomain> pointing at the host. The default environment receives <agent-id>.<baseDomain>; alternate environments receive <agent-id>-<environment>.<baseDomain>.

Lifecycle commands add deploy --prepare-only, deploy --activate, deploy --rollback, and deploy --ingress-only. Operational commands are secrets diff and agent quiesce|resume|status; host bootstrap and database transfer/upgrade are package-owned operator APIs, not framework CLI branches.

Provider: E2B (@assemblyline-agents/e2b)

sandbox/*.yaml env arrays are global passthrough variables. Validation and the Node runtime reject host/control-plane credentials such as database URLs, Railway/Hetzner credentials, E2B control keys, R2 secret keys, Photon tokens, admin tokens, and OTLP auth headers in this list. Supply capability credentials through typed connections or the per-command shell(..., { env }) scope.

Provider: Modal (@assemblyline-agents/modal)

Preview: this surface may change without notice.

Provider: Daytona (@assemblyline-agents/daytona)

Computer Use Relay (@assemblyline-agents/computer-use)

See Remote Computer Use for pairing, write policy, and relay trust boundaries.

Provider: Microsoft Teams (@assemblyline-agents/teams)