v2.58.0
Configure subagent concurrency
The maximum number of concurrently running subagents is now configurable across persistent settings, the TUI, and the dashboard. New parent sessions can also start with subagents completely disabled.
What changed
- Persistent concurrency setting.
backgroundAgents.maxConcurrentSubagentscontrols the number of children a newly started parent session may run simultaneously and defaults to4. - Zero-subagent mode. Setting the value to
0removes thesubagenttool from new parent sessions and adds explicit system-prompt guidance directing the parent model to perform normally delegated work itself. - TUI and dashboard controls. Both
/settingsand dashboard Settings display and durably save the value, with clear new-session semantics and validation feedback. - Strict validation. Negative, non-integer, non-finite, and malformed values are rejected or warned about loudly without partially changing durable settings.
- Session-isolated concurrency. Each parent session owns its concurrency gate, preventing cross-session coupling while preserving the configured limit across
/reloadand runtime rebuilds. - Regression coverage and documentation. Tests cover defaults, persistence, RPC round trips, atomic validation, configurable queueing, zero-tool startup, prompt guidance, child-session behavior, UI controls, and reload-safe gating. Public and package documentation describe the setting and its semantics.
Implemented in PR 468.