System

Config

The Context Router card — JIT context is core; the distributed component is the opt-in.

Web UI → Config (System section) holds the Context Router controls. The raw config.yaml text editor that used to live here was removed — every section of config.yaml is edited through its own structured page instead: MCP servers on MCP, the model catalog and routing on Models. To hand-edit the file itself, open <agent home>/config.yaml on the host directly.

What’s on the page

A single card, Context Router. JIT context handling is core and always on — there is no switch for it. The card configures the parts that are optional, writing <agent home>/context-router.json:

Distributed router — the cluster/swarm component (and its opt-in binary). Off by default; a default install stays two binaries.
Contract extraction — interface-contract extraction from source files. On by default.
Hot cache — the in-memory artifact cache. On by default.

SAVE ROUTER persists the switches via PUT /api/context-router/config; the card header shows the config file path it edits.

Warning

Router config is read per run — saved switches apply from the next agent run onward.

A read-only GET /api/config endpoint returns the effective config.yaml as a plain JSON object (used internally to gate optional dashboard features) — it has no write counterpart and no page of its own.

For provider API keys rather than settings, see Keys. For per-agent structured settings edited through the Agents card UI (provider, model, description) rather than raw YAML, see Agents.