A project keeps its own backend, and a run's backend is fixed when it is created #305
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
A run takes the backend in force when its first agent step starts, not when it is created;
plan.nextstarts a project's next item on whatever profile is in use then. On 2026-10-29 three runs started while Free was the active profile came up on vLLM, because the profile was switched back before their first step, and switching it at all would have moved the Breakout project's next item too.Fix
Done when
Two runs on two backends can start back to back, and a project's later items stay on its backend whatever the active profile is.
From the PR #301 verification (runs 138–143).
Confirmed on production (
6f440e5, PR #310); closing.free), the Breakout project, run 146, the one it named (main).mainwhile Free was in use, and its first agent step,plan.write.auto, ran on vLLM (qwen3.8-27b). Before, a run took the profile in use at its first agent step.cmoriarty/breakout-planned-2 runs on vLLM · qwen3.8-27b, with the select to change it.main.mainwas back in use by then, so the case where the two differ rests ontests/api/test_run_profile.py.Left over, filed as #313: the context per agent, the run limit and the engine probe still follow the profile in use. With Free in use, the project queued behind a Free run under Free's run limit of 1.