Repository navigation
Description
What happens
Attach a Harness, then pick Model API in AI source. The source row updates — the popup reads "Model API", the state line reads "Not attached." — and the Base URL, Model and API key rows below stay frozen. Typing into Base URL does nothing. Only a relaunch hands them back.
It fails in both directions. Start with no Harness, pick Harness · claude, wait for it to attach: the three rows stay editable while the Harness is the Completer.
Why it matters
The section's own copy promises the opposite:
Off above hands the HTTP rows back, and takes effect at once.
That sentence is the whole point of #500 — the wait is bounded by the user, not by a relaunch. On AppKit the wait is still a relaunch.
Cause
form::describe() is rebuilt on every draw, so http_row_parts reads harness::driving() live and the frozen flags in the description are always current. The AppKit renderer only ever reads them once:
frozenis applied in the build pass —settings_window.rs:791,:834,:869,:958,:1026,:1073.draw()(settings_window.rs:505) sets values and placeholders. It never callssetEnabledorsetEditable.
Closing and reopening Settings does not help: the window is hidden and reshown, not rebuilt.
Verified on
macOS 15 (Darwin 25.6), AppKit renderer, main at d152097e and on #593. Pre-existing, not from either.
scripts/verify-settings-macos.sh (once #626 lands) covers the launch-time half of this — it opens Settings after the Harness attaches for exactly this reason. The runtime switch is what it cannot cover until this is fixed.
Not just this
Two smaller things share the cause and are worth folding in:
- A frozen text field looks live.
freeze_or_bindfreezes withsetEditable(false), which leaves the field at full contrast with a normal border — indistinguishable from an editable one until you type into it. The popups next to it grey out properly. Thestatusstrips (FormRow::status) exist in the data and no renderer draws them, which is where the "not in use" explanation was supposed to go. - GTK and Win32 need the same check. Both build their controls in one pass too; whether they re-apply on redraw is unverified from here.
What "done" looks like
draw() re-applies frozen for every row it can reach, so switching AI source freezes or unfreezes the three HTTP rows in place — no relaunch, and no stale copy telling the user it already happened.
Metadata
Metadata
Assignees
Labels
Projects
- StatusShow more project fieldsDone
Activity
omesser commentedon Sep 11, 2026
Fixed by
015cc5f7on #593, verified live on macOS at tipeb77f282.draw()now re-appliesfrozenon the redraw path —setEditable(!frozen)for fields,setEnabled(!frozen)for popups and buttons — so the rows follow the AI source picker without a relaunch. Driven in an open window:The direction this issue quotes — "hands the HTTP rows back, and takes effect at once" — is the five-second one. The freeze direction lags about a minute behind the attach because it waits for the next redraw rather than riding the attach, which is a smaller thing than what this issue describes and not worth holding it open.
The
statusstrips render now as well: "Not in use: a Harness is the Completer" appears under the frozen rows, which was the other half of the complaint — a frozen field is still visually identical to a live one, but it is no longer unexplained.Two things this does not cover: the GTK and Win32 halves of the same commit, which cannot be compiled on the machine that verified this.
Closing on the strength of the macOS verification. #593 is still open — if it does not land, this comes back with it.
— Claude Code, on @omesser's behalf