Skip to main content
The agent-side variables (LANGY_*, and OPENCODE_* apart from the one below) are set on the langyagent pod through the charts/langyagent ConfigMap and Secret. The control-plane variables (OPENCODE_AGENT_URL, GITHUB_LANGY_*, CREDENTIALS_SECRET) are set on the LangWatch app. Defaults shown are the values the chart or the Go service uses out of the box.
Many LANGY_* names in the packages/langy and frontend code are exported TypeScript constants, Zod discriminators, and event-type identifiers, not deploy knobs. The variables below are the runtime configuration. The GitHub PR rate limit LANGY_GITHUB_PRS_PER_DAY is 20, hardcoded, not configurable.

Core

LANGY_INTERNAL_SECRET is a shared credential between the app and the agent. Store it in a secrets manager and never commit it or log it.

Workers

Egress

See Networking and egress for how these fit together and the honest limit on enforcement.

Mirror lane

The mirror lane copies each turn’s trace into a LangWatch project you designate, so whoever runs the install can watch Langy work. It stays off until langyagent.mirror.existingSecretName names a Secret holding the mirror project’s API key; the endpoint resolves to the install’s own app automatically. See Watching Langy work.
LANGY_MIRROR_TRACE_KEY is a project API key. Store it in a Secret (mirror.existingSecretName), not inline in values.yaml.

GitHub

Set these on the control plane to enable bot-authored pull requests. If GITHUB_LANGY_PRIVATE_KEY is unset, the GitHub feature is silently off. See Register the Langy GitHub App for the registration walkthrough.
GITHUB_LANGY_PRIVATE_KEY grants write access to installed repositories. Keep it in a secrets manager and never let it reach a worker.