A project keeps its own backend, and a run's backend is fixed when it is created #305

Closed
opened 2026-10-29 15:32:32 -04:00 by cmoriarty · 1 comment
Owner

What happens
A run takes the backend in force when its first agent step starts, not when it is created; plan.next starts 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

  • A project saves the backend it was started with, and its runs use it by default; the operator changes it on the project.
  • A run's settings copy is written when the run is created, not at its first step.

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).

**What happens** A run takes the backend in force when its first agent step starts, not when it is created; `plan.next` starts 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** - A project saves the backend it was started with, and its runs use it by default; the operator changes it on the project. - A run's settings copy is written when the run is created, not at its first step. **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)._
Author
Owner

Confirmed on production (6f440e5, PR #310); closing.

  • New Run has a Backend select listing the six backends, defaulting to the profile in use.
  • A run records its backend when it is created: run 145 took the profile in use (free), the Breakout project, run 146, the one it named (main).
  • The fix itself: run 146 was created on main while 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.
  • The project page reads cmoriarty/breakout-planned-2 runs on vLLM · qwen3.8-27b, with the select to change it.
  • Item runs take the project's backend: run 147, the project's first item, recorded main. main was back in use by then, so the case where the two differ rests on tests/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.

**Confirmed on production (6f440e5, PR #310); closing.** - **New Run** has a Backend select listing the six backends, defaulting to the profile in use. - **A run records its backend when it is created:** run 145 took the profile in use (`free`), the Breakout project, run 146, the one it named (`main`). - **The fix itself:** run 146 was created on `main` while 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. - **The project page** reads `cmoriarty/breakout-planned-2 runs on vLLM · qwen3.8-27b`, with the select to change it. - **Item runs take the project's backend:** run 147, the project's first item, recorded `main`. `main` was back in use by then, so the case where the two differ rests on `tests/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.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
cmoriarty/braid#305
No description provided.