Global Configuration

Overview

global: contains Router-wide settings and shared infrastructure. It is the counterpart to the route-local routing: tree: define a service or store once under global:, then opt individual routes into it with signals, algorithms, or plugins.

Key Advantages

• Defines shared infrastructure once for all recipes and routes.
• Keeps route-local policy separate from platform-wide services.
• Makes model, storage, and external-service dependencies explicit.

What Problem Does It Solve?

Embedding runtimes, APIs, storage backends, observability, and helper services are shared resources. Keeping them outside decisions avoids duplicated connections and makes the data and trust boundaries visible.

When to Use

Use global: for behavior or infrastructure shared by several recipes. Keep route matching, candidate models, algorithms, and plugins in routing:. Global settings are shared across recipes; signals, projections, and decisions are recipe-scoped, while algorithms and plugins belong to individual decisions.

Configuration

global:
  services:
    observability:
      metrics:
        enabled: true
  stores:
    response_cache:
      enabled: true
      backend_type: memory

Global configuration has five groups:

Group	Owns	Guide
global.router	Router engine controls, selection defaults, streamed-body policy, learning	Algorithms, Router Learning
global.services	API, Response API, observability, authz, rate limits, management API, startup status, replay	API and Observability
global.stores	response cache, memory, vector store	Stores and Tools
global.integrations	tool catalog and Looper endpoint/state	Stores and Tools
global.model_catalog	embeddings, system models, external helpers, knowledge bases, capability modules	Safety, Models, and Policy

Entrypoints and named recipes are top-level objects rather than global settings; see Virtual Models. Remote text embeddings are covered in Remote Embedding Providers.

Operational Boundaries

• Keep overrides sparse; omitted fields inherit Router defaults.
• Put credentials in environment variables or Kubernetes Secrets, not literal YAML values.
• Persistent stores may contain prompts, responses, embeddings, memories, or replay records. Set backend authentication, transport security, retention, and tenant/user scope deliberately.
• providers.defaults.reasoning_families and providers.models[].reasoning_family are provider configuration, not global: configuration.
• See the complete configuration reference in config/config.yaml.