Repair keeps the backend a run started with, so changing Repair in Settings doesn't reach a run that has failed #325
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
Run 157 (Free, thorough) failed. Asking Repair "why did this step fail?" was refused: "Repair cannot use the Free profile yet: choose another backend for Repair in Settings." The operator then set Repair to vLLM and saved. The same refusal came back.
repair_backendis one of the run's snapshot fields (RUN_SNAPSHOT_KEYS), frozen when its first agent step starts, because its opencode server is configured with the Repair provider then. A run started on Free can never be repaired, whatever Settings says after.Fix
Repair reads its backend from the settings now, not the run's copy. When that differs from what the run's server was configured with, Repair renders the run's opencode config again with the
repairprovider before its session. Repair works after the run, so restarting the run's server is fine.Done when
On a failed Free run, choosing vLLM for Repair in Settings and asking again gets an answer. A test covers the backend changing after the run started.
Confirmed on production (
add5fd1, PRs #328 and #330); closing. Run 157 started on Free while Repair followed Free. With vLLM then chosen for Repair, its Repair answered fromqwen3.8-27b: "The run failed at theagent.code-reviewstep: all five of its attempts died on the very first model call with a 401provider.auth..." That diagnosis is right; see #331. It took two fixes: Repair now reads its backend when asked (#328), and a Free run's config carries therepairprovider (#330).