Skip to main content
The Config panel reads the live configuration from inside the running agent and lets you edit it as JSON.
The agent must be running. The panel reads from the container, not from a copy in a database — there is no stale second version of this file anywhere.

​
The platform writes it once

A starting configuration is written on the agent’s first boot only. After that the file belongs to the agent, and nothing on the platform overwrites it — not a redeploy, not a version upgrade. That is why editing it is safe: your changes are not going to be reverted by the next deploy.

​
What the platform still owns

Three subtrees carry key references the platform fills in at deploy time:
The editor shows them and refuses to save an edit that changes them. Editing them by hand would replace a working key reference with a literal that the next deploy cannot resolve. Change the model or the provider from Model and key instead.

​
Four ways a save lands

The agent decides which, and the panel reports what actually happened: The two disruptive outcomes are confirmed before they happen, and the dialog says which one it is — “Saving restarts the agent. Whatever it is doing right now stops.” There is a fifth: saved, but not applied. Some keys are read only at startup, so the value is stored and takes effect the next time the agent boots. The panel names those keys rather than claiming success.

​
When the agent refuses

The last row is the important one. A config the platform could not validate is not written — a gateway that fails to start on a bad config leaves an agent that cannot be reached to fix it.

​
Undo

Reload from agent discards your edits and re-reads the live file. The summary above the editor — “What this agent is set to” — is generated from the current config, so you can check the effect of a change without reading the whole file.
Last modified on August 31, 2026