Only one backend is saved at a time: keep backends as named profiles, so trogdor and the Claude API are one click apart #161
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?
Settings hold one main backend and one planning backend. Moving from trogdor to the Claude API means retyping the kind, URL, model, window, output reservation and effort, and moving back means retyping trogdor's, which nobody remembers. Since #160, moving the URL to another host also removes the pasted key, so it has to be pasted again too.
What it needs
vLLM · qwen3.8-27b), and a separate planning backend becomes a second one, so nothing is lost on upgrade.Done when
trogdor and the Claude API are both saved as profiles, switching between them on the Settings page takes one click and no retyping, both keep their keys, and a run started after a switch uses the new profile while one already running keeps its own.
Shipped in
da22c2c(deployed; new boot id). Change archived asopenspec/changes/archive/2026-10-09-backend-profiles.What shipped
vLLM · qwen3.8-27bwith its saved 524,288 window and 32,000 reservation.Found and fixed on the way: a context per agent saved together with a wider window was judged on the old window; and after saving a new backend with a typed key, Use for runs stayed disabled until a reload (the settings spec now covers it, and fails without the fix).
Checked: browser check on a local stack upgraded from #160-era settings (two runs kept the backend each started on; both keys and a rename survived an osfd restart); full lane green (backend, 188 browser specs, 13 simulated runs).
Next: #162 builds the Connect flow and per-model defaults on these profiles.