Runtime configuration

The standalone binary loads its generated configuration from embedded values and the process environment when a command uses it. Configuration fields come from the selected components and the manifest. Changes to environment variables take effect when configuration is loaded again.

Use the config command to inspect resolved values.

Configuration shape

The tables below describe configuration paths in the generated binary. Fields marked manifest value take their value or runtime fallback from the resolved manifest. A field listed as conditional is generated only when its corresponding configuration is present.

… indicates a required value with no default. null indicates an optional value. Fields with types linked below have their own shape definitions on this page. JSON value means arbitrary JSON data whose structure is defined by its consumer.

Config

Inspect a particular binary with the config command. Custom blocks can contribute additional configuration fields.

AgentConfig

Path: agent.

AgentModel

Path: agent.model.

PromptConfig

Path: agent.prompt.

LangfusePromptConfig

Path: agent.prompt.langfuse. Optional settings below are generated when supplied by the resolved prompt configuration. Their values and runtime fallbacks follow the Langfuse prompt source.

ProviderConfigs

Path: provider. Each generated field is the configuration key of a declared provider. Provider labels containing punctuation are converted to snake case for this key.

ProviderConfig

Path: provider.<provider_key>. Only configured fields are generated. Values and runtime fallbacks come from the corresponding provider declaration.

Model keys replace each non-alphanumeric character in the model name with _. For example, google/gemma-2-2b-it becomes google_gemma_2_2b_it. A model's settings live directly under this key, such as provider.cloud.google_gemma_2_2b_it.temperature.

InferenceParams

Only configured parameters are generated. Each takes its value or runtime fallback from the corresponding provider or model declaration.

ToolConfigs

Path: tool. Each generated field is the configuration key of a JavaScript, Python, or Bash tool. Tool labels containing punctuation are converted to snake case for this key.

ToolConfig

Path: tool.<tool_key>. Values and runtime fallbacks come from the tool declaration.

ServerConfig

Path: server. Defaults apply when the corresponding HTTP server field is omitted.

FilesystemConfig

Path: filesystem.

FilesystemBind

Path: filesystem.binds.<index>.

NetworkConfig

Path: network. Defaults below apply when the corresponding network fields are omitted. Manifest values can replace them.

NetworkLimits

Path: network.limits.

NetworkPolicy

Path: network.policy.

NetworkAddresses

Path: network.policy.addresses.

NetworkUrlPattern

Path: network.policy.allow.<index>.

A null component matches any value. See URL patterns for pattern syntax.

export AGENT__NETWORK__POLICY__ALLOW__0__HOSTNAME=somehost.com

McpConfig

Path: mcp.

McpStdioTransport

Path: mcp.servers.<label> when type = stdio.

McpHttpTransport

Path: mcp.servers.<label> when type = http.

A2aConfig

Path: a2a.

A2aAgent

Path: a2a.agents.<label>. Manifest values and runtime fallbacks take precedence over the defaults below.

A2aTenant

Path: a2a.agents.<label>.tenant.

inherit forwards the caller's effective tenant. none sends the request without tenant identity. fixed forwards id.

DatabaseConfig

Path: database. Available with the ReAct graph.

The CLI reference defines the migration command and the --no-migrations override.

DatabaseOptions

Path: database.options. When this entire setting is omitted, optional limits are null and enable_logging is false. When supplying an options object, include enable_logging.

Duration

For example, configure a ten-second connection acquisition timeout:

export AGENT__DATABASE__OPTIONS__ENABLE_LOGGING=false
export AGENT__DATABASE__OPTIONS__ACQUIRE_TIMEOUT__SECS=10
export AGENT__DATABASE__OPTIONS__ACQUIRE_TIMEOUT__NANOS=0

ReActConfig

Path: react. Available with the ReAct graph.

ReActModelConfig

Path: react.model. Configured graph model values supply embedded values or runtime fallbacks.

ReActRetryConfig

Path: react.model.retry. All three fields are required when a retry policy is supplied.

TaskQueueConfig

Path: task_queue. Available with the ReAct graph and HTTP server.

MemoryPubSub

Path: pubsub. Available with the ReAct graph and HTTP server. The whole section defaults to kind = memory and capacity = 4096. Supplying the section explicitly requires both fields.

RedisPubSub

Path: pubsub when kind = redis.

export AGENT__PUBSUB__KIND=redis
export AGENT__PUBSUB__URL=redis://localhost:6379/1

Fixed and runtime values

For manifest expression syntax, see Runtime values.

Fields supplied by configuration sections also have their own defaults. A field's manifest or component reference defines its settings and defaults.

Environment variable names

The prefix is AGENT__. Separate nested field names with __ and write them in uppercase:

The field must be present in the binary's generated configuration and permit environment values. For example, server fields are generated when the HTTP server is enabled.

A runtime("NAME", ...) expression also maps NAME to that field. Both the named variable and its AGENT__... form address the same setting. When both set that setting, the named variable wins.

http_server {
  port = runtime("HTTP_PORT", 8080)
}

export AGENT__SERVER__PORT=8081
export HTTP_PORT=9090

The resolved port is 9090. With both variables unset, it is 8080.

Aliases also support nested keys and list positions using the same __ separator. For example:

network {
  policy {
    allow = runtime("ALLOW", [])
  }
}

export ALLOW__0__HOSTNAME=somehost.com
export ALLOW__0__PORT=8080

These variables set the first allowed URL pattern's hostname and port. ALLOW__0__PORT addresses the same field as AGENT__NETWORK__POLICY__ALLOW__0__PORT.

Value formats

Write scalar values as text. Numbers are parsed into the field's numeric type, and true or false set boolean fields. Lists and maps accept delimited field paths or JSON values:

export AGENT__DATABASE__AUTO_MIGRATE=false
export AGENT__DATABASE__REPLICAS__0=postgresql://user:password@replica:5432/dbname

Nested keys address individual fields. Numeric segments address list positions, as 0 does above.

Alternatively, supply a complete list or map as a JSON value:

export AGENT__DATABASE__REPLICAS='["postgresql://user:password@replica:5432/dbname"]'

When both a parent value and a nested value are supplied, the parent is applied first and the nested value is applied afterward.

An empty environment value unsets its configuration path after embedded defaults are applied. The field's type and defaults determine the resulting value or missing-value error.

Configuration errors

Configuration loading fails when a required value is missing, a value cannot be parsed into its field's type, or an environment variable attempts to change a fixed value. The error identifies the affected configuration path.

Settings references

Observability variables are read separately from the generated configuration and use the names listed in their reference.