A run's context per agent and run limit come from the profile in use, not the run's #313
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
Since #305 a run keeps the backend it was created with, and its server is set up from that profile. A few settings are still read from the profile in use while the run goes: the context per agent (which sizes sessions and picks the apply mode), the run limit,
mediation_max, and the engine probe, which checks only the backend in use. On 2026-10-29, with Free in use, the Breakout project (run 146, on vLLM) queued behind a Free run under Free's run limit of 1 (main's is 3), and a step it starts then is sized by the flat 150,000 tokens per agent, not main's 400,000.Fix
Read these from the run's recorded profile. Count the run limit per backend, so runs on different backends don't wait for each other (with #306). Probe each backend a going run uses.
Done when
A run started on one profile while another is in use is admitted, sized and probed by its own profile, in a test and on production.
Confirmed on production (
1fc0f22, PR #319); closing.breakout-planned-3recordedmain.openspec.proposekept running on vLLM, holding its slot, with no hold.