Admin Dashboard: Config

Config imports, exports, and reloads the supported platform configuration. Use it for review, environment promotion, and recovery—not as a secret store or a replacement for a database backup.

Hot reload

Choose Hot Reload after changing configuration outside Admin. The new agent and integration configuration becomes available without restarting the service. Changes made normally through Admin or the management MCP server are already synchronized and do not need a reload.

The result reports how many agents were loaded. A successful reload does not validate an external MCP server or model provider, so test the affected schema afterward.

Export

Choose Export Configuration to preview, copy, or download YAML. The export includes your agents and their built-in-tool assignments, models, MCP servers, schemas and relations, and Knowledge Graph bundles. It does not include agent capability settings, knowledge bases or documents, settings, API tokens, active sessions, or secrets such as provider API keys.

For each Knowledge Graph entity type, configuration export and brewctl kg pull currently include at most 500 entities. Keep the maintained bundle directory or export every REST page when you need a complete copy of a larger graph.

Import

Export the destination before a substantial change.
Review names, dependencies, relations, and any full Knowledge Graph payloads.
Paste the YAML into Import Configuration and import.
Read the resource counts and reload result.
Test the affected schema.

The import merges supported resources with existing configuration. It is not a universal delete-and-recreate operation, and system-managed schemas do not round-trip as customer-owned resources. Models, MCP servers, agents, and schemas are committed before Knowledge Graph bundles are applied; if a graph fails validation, those earlier changes remain in place. Read the error, correct the bundle, and import again.

Promotion workflow

Export the source environment and remove environment-specific values.
Review the YAML in version control without adding secrets.
Validate and preview with a pinned brewctl version when the resource is supported there.
Import or apply to a non-production workspace first.
Re-enter destination credentials through the approved secret workflow.
Test models, MCP connectivity, schema relations, Knowledge capability links, and a representative chat.

Keep the reviewed source bundle as the intended configuration. Do not treat an export as an exact database snapshot: it intentionally omits credentials and several resource families.

Operational cautions

A secret-free export is not a complete disaster-recovery backup; back up PostgreSQL separately.
Keep delegation in schema relations, not a writable can_spawn field.
Knowledge documents use their dedicated upload workflow. A Knowledge Graph import is a full bundle reconciliation and can remove omitted entities. Do not use a config export to restore a graph with more than 500 entities of one type.
Use brewctl diff before declarative applies and pin the CLI/runtime versions used by CI.