A profile saved before #274 runs with Free's run settings: one session at a time, 4 subagents, 179k per agent #341
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
The fastllm profile was saved before profiles kept run settings (#274), so it holds only backend fields. Its runs take every run setting from the flat values, which are Free's while Free is in use. Run 160 (fastllm, thorough) recorded
parallel_sessions: 1,max_subagents: 4andapply_mode: single. Its budget uses Free's 179,520 context per agent (alarm 149,520) instead of a size from fastllm's 262k window. So its proposal review ran as one combined reviewer ("the backend serves one session at a time"), and fastllm's 6 slots go unused. The exl3 profile is the same.Fix
A profile without its own run fields takes the defaults, never Free's. Fill old profiles' missing run fields when settings load, and show them on the Settings page.
Done when
A run on an old profile, started while Free is in use, records the defaults in its
settings.json, and its proposal review runs the four lenses on a backend with more than one slot.Seen again, and made worse by a save: at 13:08 today a Settings save made fastllm the profile in use. It was its first save since #274, so it stored the flat values it had been reading, Free's, as fastllm's own: 1 parallel session, 4 subagents, 179,520 per agent, 2 runs, apply
single. The page gave no sign the values came from Free.Worked around for fastllm only, at the operator's request: the fastllm profile now holds its own run settings (6 parallel sessions for
--max_batch 6, 5 subagents, 200,000 per agent, 3 runs, applyauto). It was saved through the profile list, so Free's flat copy is unchanged. The exl3 profile still has no run fields and still reads Free's.Shipped in PR #356 (
c00c62f1, live on production).