System-Wide Configuration

Where system context is background information for your agents, system-wide configuration is a set of global parameters your workflows read at runtime — the operational defaults you'd rather not hard-code into individual workflows. Think default revision limits, default cost ceilings, or any other named value your workflows want to look up.

Keys and values

Each parameter is a key/value pair with an optional description. You type a key and the app normalises it to uppercase snake_case (spaces become underscores; letters and numbers only), so max revision rounds becomes MAX_REVISION_ROUNDS. Both the key and the value are stored as plain text — there's no special typing; a value is just a string. Keys must be unique; a duplicate is rejected.

Enabling, editing, deleting

Like system context, each parameter has an enabled/disabled status, and only enabled parameters are included in workflow runs — and only for executions that start after the change. Disabling and deleting ask for confirmation, and a deleted parameter can't be brought back with an undo.

Global defaults, per-workflow overrides

These parameters are global: every workflow can read them at start time. But a workflow doesn't have to accept the global value — a workflow can override specific parameters for itself, so a shared default (say, a cost limit of 5.00) can be raised or lowered for one particular workflow without changing it for everyone else. When a run starts, Circus resolves the effective value — the override if one exists, otherwise the global — and captures both in the execution's snapshot, so you can always see what was global, what was overridden, and what actually applied.