The team3 weeks ago
Thanks: your idea is implemented and ships in the next release. We built it the way we pictured it, so if the result is not what you had in mind, tell us and we will adjust it.
Done
Make the per-project limit of 8 throwaway agents configurable
From XawierDone 3 weeks ago
When an orchestrating agent calls agents_spawn, AgentsRoom refuses once the project has 8 throwaway agents running ("this project already has 8 throwaway agents running (limit 8)"). There is no setting for this cap: settings_list (global and project scope) has no key for it.
Our workflow: one coordinator agent works through the backlog overnight, with implementer agents and dedicated reviewer agents per ticket. With only 8 slots, reviewers and implementers compete for them. New tickets from the user wait even when the machine has headroom, and the coordinator has to juggle agents by hand.
Request: a setting for the maximum number of concurrently running throwaway agents, with a global default and a per-project override, also available through settings_set / MCP (e.g. 1-32, default stays 8). Nice to have: the refusal message names the setting.