System configuration

In this page

A few parts of the stack are configured outside .env: the LLM gateway needs a config.yaml listing its providers, PeerDB needs its replication mirrors running, and Temporal workers can be tuned for throughput. This page covers all three. Set your secrets and provider keys in Environment Variables first, since the config here references them.

LLM Gateway

The gateway is a Go proxy that routes every model call the platform makes. It reads a config.yaml that lists which providers it may use and which models each exposes.

cp agentcc-gateway/config.example.yaml \
   agentcc-gateway/config.yaml

volumes:
  - ./agentcc-gateway/config.yaml:/app/config.yaml:ro

docker compose up -d --force-recreate gateway

Provider Examples

providers:
  openai:
    api_key: "${OPENAI_API_KEY}"
    api_format: "openai"
    models: [gpt-4o, gpt-4o-mini]

  anthropic:
    api_key: "${ANTHROPIC_API_KEY}"
    api_format: "anthropic"
    models: [claude-opus-4-5, claude-sonnet-4-5]

  gemini:
    api_key: "${GOOGLE_API_KEY}"
    api_format: "gemini"
    models: [gemini-2.0-flash, gemini-1.5-pro]

providers:
  bedrock:
    api_key: "${AWS_SECRET_ACCESS_KEY}"
    api_format: "bedrock"
    region: "${AWS_REGION}"
    access_key: "${AWS_ACCESS_KEY_ID}"
    models: [anthropic.claude-3-5-sonnet-20241022-v2:0]

providers:
  vertex:
    base_url: "https://us-central1-aiplatform.googleapis.com"
    api_key: "${GOOGLE_ACCESS_TOKEN}"
    api_format: "gemini"
    headers:
      x-gcp-project: "${GCP_PROJECT_ID}"
      x-gcp-location: "us-central1"
    models: [gemini-2.0-flash-001]

For routing rules, rate limits, caching, and the full config reference, see Agent Command Center → Self-Hosted.

PeerDB Replication

PeerDB continuously replicates Postgres tables into ClickHouse (change-data-capture) so trace and eval analytics stay fast. It runs on its own. The only thing you typically touch is a first-boot timing fix.

docker compose logs -f backend                       # wait for "Application startup complete"
docker compose run --rm peerdb-init bash /setup.sh   # re-run init

Verify at http://localhost:3001. Mirrors should move to running within seconds. Re-run the same init command after any upgrade that changes replicated tables.

Temporal Workers

Temporal runs the platform’s background jobs and evaluation pipelines. How those jobs are distributed across workers depends on one flag.

All-queue (default). One worker polls every task queue. Controlled by TEMPORAL_ALL_QUEUES=true in .env. This is the right setup for most self-hosted deployments.

Per-queue (dev overlay). Six dedicated workers, one per queue, brought up by the dev overlay:

Tune throughput with TEMPORAL_MAX_CONCURRENT_ACTIVITIES and TEMPORAL_MAX_CONCURRENT_WORKFLOW_TASKS in .env. The Temporal UI is available in dev mode at http://localhost:8085.

Dive Deeper