Flows

Settings → Flows (/admin/settings/ai/flows) governs dynamic flows — multi-participant agent runs that an agent authors on the fly, rather than the curated definitions in the Flow catalog. This page is the kill switch plus the clamp profile that bounds every dynamic run: how many participants, how many rounds, how much budget, how long each round can take. Curated catalog definitions are exempt from these clamps.

Dynamic flows

Key	Range	Default	Description
Flows:Dynamic:Enabled	bool	true	Master switch. When off, no new dynamic flow can start (existing runs finish).
Flows:Dynamic:MaxParticipants	int 1–8	3	Most participant roles a dynamic flow may declare; a flow asking for more is rejected at start.
Flows:Dynamic:MaxActiveRunsPerUser	int 1–20	2	How many dynamic flows one user can have running at once.
Flows:Dynamic:MaxRounds	int 1–50	10	Ceiling on rounds per flow; a flow requesting more is clamped down to this.
Flows:Dynamic:BudgetUsd	decimal ≥ 0	5	Spend ceiling per flow, in USD; a flow requesting a larger budget is clamped to this.
Flows:Dynamic:RoundTimeoutCapMinutes	int 1–60	15	Upper bound on any single round’s timeout; a longer requested timeout is clamped to this.
Flows:Dynamic:RoundTimeoutDefaultMinutes	int 1–60	10	Round timeout applied when a flow doesn’t set its own.
Flows:Dynamic:IdleTtlCapHours	int 1–24	2	How long an idle flow lives before it’s reaped; also the default when a flow doesn’t set one.
Flows:Dynamic:ModelAllowlist	string, comma-separated	empty = no restriction	If set, participants may only use these models; a flow naming any other model is rejected. Empty allows any priced model.

Setting Flows:Dynamic:Enabled to false is the kill switch: no new dynamic flows can start. The cap settings are applied to every dynamic definition as it starts, so lowering a cap tightens runs that begin afterward.

Related

• Flow catalog — the curated definitions that are exempt from these clamps.
• Review flows — the user-facing feature these settings bound.