With Free in use, Settings refuses every save #312
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What happens
While the Free profile is in use,
POST /api/settingsrefuses any save that keeps it in use: "cannot delete free: runs use it; choose another first". The check that the profile in use is not being deleted looks for it among the saved profiles, and Free is listed, never saved, so it always looks deleted. Seen 2026-10-29 raising the run limit with Free in use; only switching to another profile saves.Fix
Count Free as present in the in-use checks (runs, planning, Repair) when its router is configured. Decide where Free's run settings live (run limit, context per agent, subagents): today they are the flat copy, which no page edits once profiles exist.
Done when
With Free in use, a run setting saves from the Settings page, and a test covers it.
Confirmed on production (
1fc0f22, PR #319); closing. With Free in use,POST /api/settings {run_cap: 2}saved, and the settings read backin use free, run_cap 2. Before, every such save was refused: "cannot delete free: runs use it".mainwas put back in use afterwards, with its own run limit of 3 untouched.