For the complete documentation index, see llms.txt. Markdown versions of all docs pages are available by appending .md to any docs URL.

Look up the environment variables that each kagent component reads, including their types and defaults.

Review the environment variables that a kagent installation reads, grouped by the component that reads them.

Most of the following variables have a Helm chart setting that writes them for you, and the chart setting is the supported way to set them. Use a variable directly only whenever you run a component outside the cluster, such as kagent db against a database from your own machine, or when a variable has no chart setting.

Default values describe the component on its own. Helm, or an agent’s HarnessHarnessA Kubernetes custom resource defining how an agent is allowed to run: which harness executes the agent, its workload image, and its WorkerPool and snapshot storage. An Agent pairs it with the AgentTemplate that it runs.Learn more spec.env, might supply a different value, so the default listed here is not the guaranteed value that a running installation might use. (none) means the variable has no fixed default, so read the description for what happens when it is unset. A variable that more than one component reads appears under each of them.

Credentials, controller-generated runtime payloads, and internal process wiring are not configurable settings and are not listed.

Controller

The kagent controller reads these variables at startup. Helm writes most of them into the controller ConfigMap, so prefer the matching chart value where one exists. Set the variable directly only for a setting the chart does not expose. For the chart values, see the Helm reference.

Agent runtime

The kagent controller supplies these variables to each agent runtime that it schedules. Setting one of them in a Harness spec.env does not override the controller on a managed runtime, because the controller writes its own value into every revision it compiles. The byo runtime is the exception because the controller sends it no configuration, so it reads whatever spec.env holds. For more information, see Agent harness.

CLI

The kagent command line tool reads these variables from the environment that it runs in. Each one has an equivalent flag where the command takes a flag, and the flag wins when both are set.

UI

The UI container and the Vite development server read these variables. Values prefixed KAGENT_UI_ that reach the browser are public, so none of them can carry a secret.