Configuration

Configure the agent entirely through environment variables. Start with the core LLM settings, then add provider keys, access control, and persistence as you need them.

Core LLM settings

These three variables cover most deployments.

LLM_API_KEY=sk-or-...
LLM_API_BASE=https://openrouter.ai/api/v1
LLM_MODEL=openrouter:openrouter/auto

Provider-specific keys

Set the key for each provider you want to use. Only providers with a key configured appear as selectable in the model picker.

Extra models

LLM_EXTRA_MODELS adds entries to the model picker without touching code. Format:

provider:modelId[|contextLength][|description]

• provider — one of openrouter, nvidia, anyrouter
• modelId — model ID passed to the provider (may contain colons)
• contextLength — optional integer token count; defaults to 128000
• description — optional display label; defaults to modelId

Comma-separate multiple models:

LLM_EXTRA_MODELS="nvidia:meta/llama-3.3-70b|131072|Llama 3.3 70B,openrouter:x-ai/grok-2"

Extra models are appended after the built-in registry. If an extra entry shares a provider:modelId key with a built-in, the built-in wins.

Access & safety

Require auth on public deployments:

CHM_FEATURE_AGENT_ACCESS=authenticated

Protect the API endpoint with a bearer token:

AGENT_API_TOKEN=your-secret-token

curl -H "Authorization: Bearer $AGENT_API_TOKEN" \
     -d '{"message":"...","hostId":0}' \
     https://your-host/api/v1/agent

Least-privilege ClickHouse user

The agent's query tool (and the MCP server) run read-only SELECTs that the model composes. Because the model can read any table the connection user can, point it at a dedicated, restricted user — not default or an admin account. Two concerns in particular:

• system.query_log can contain credentials embedded in query text (e.g. a CREATE ... IDENTIFIED BY or an s3(...) call another client ran).
• system.users, system.grants, and system.quotas expose your access model.

Create a monitoring user restricted to the system tables the dashboard needs and deny the sensitive ones:

CREATE USER chmonitor_agent IDENTIFIED BY 'a-strong-password'
  SETTINGS readonly = 1;

-- Read-only access to the metrics/monitoring tables the dashboard reads.
GRANT SELECT ON system.* TO chmonitor_agent;

-- Revoke the tables that leak secrets or your access model.
REVOKE SELECT ON system.query_log FROM chmonitor_agent;
REVOKE SELECT ON system.users FROM chmonitor_agent;
REVOKE SELECT ON system.grants FROM chmonitor_agent;
REVOKE SELECT ON system.quotas FROM chmonitor_agent;

Conversation persistence

For per-backend env vars and setup, see Conversation history and Store backends.

Where to set these

• Cloudflare Workers — wrangler secret put LLM_API_KEY for secrets; [vars] in wrangler.toml for non-secret values in your own worker. (In this repo's hosted deploy, non-secret config lives in apps/dashboard/.env.production and there is no [vars] block.) See Deploy to Cloudflare.
• Docker — environment: block in docker-compose.yml or --env-file .env. See Deploy with Docker.
• Kubernetes — Secret for keys, ConfigMap for non-secret values. See Deploy to Kubernetes.
• Vercel / self-hosted — environment variables in the project dashboard or .env.local.

Related