Edit model roles from the dashboard #860

Closed
opened 2026-10-27 13:38:03 +00:00 by sam · 0 comments
Owner

Let an operator point a model role (planner, builder, reviewer, embedding) at
a different provider/model from the dashboard, without hand-editing
config.toml.

Concrete need: switching this repo's work off a given provider currently means
editing [models] on the host. The dashboard already shows every provider the
catalog discovered, which makes the absence of a control the obvious gap.

Why this is a small slice once writes exist:

  • Models is map[string]string, addressed by the whole dotted key "models",
    exactly the shape that made Repos writable in archie-core-b6ew.6 via
    UpdateConfig(ctx, {"repos": repos}). No array-index overlay support needed.
  • Models is already in reloadableFields (internal/app/archied/reload.go:147),
    and ForTask rebuilds the per-task snapshot from d.Cfg.Get() at dispatch, so
    a write takes effect on the next task with no restart.
  • The candidate values are already computed: applyModelCatalog returns the
    sorted provider/model refs as b.catalogModels, and cfg.Providers is merged
    with everything the catalog discovered, so the picker has its options
    without new discovery.
  • config_schema.go currently marks models FieldStructured/Editable:false.

Scope: role -> model ref only. Not adding or removing providers, not editing
credentials, not chat.models.

Blocked by archie-core-j28m: the UI process has no write path at all
(UpdateConfig/ResetConfig/UpdateRepoField are nil in production and
compose_test.go asserts they stay nil), so this cannot land until that bead
picks a transport.

Acceptance: changing builder from one provider/model to another in the
dashboard persists, republishes the snapshot so the page does not show the
operator their own edit missing, and the next dispatched task uses it without
a daemon restart. An unknown model ref is rejected before persist.

Close reason

Closed


Imported from beads archie-core-1786637498420-327-bacadaae.1 · GitHub #941 · type task · priority P2 · created 2026-09-18 · closed 2026-10-05

Let an operator point a model role (planner, builder, reviewer, embedding) at a different provider/model from the dashboard, without hand-editing config.toml. Concrete need: switching this repo's work off a given provider currently means editing [models] on the host. The dashboard already shows every provider the catalog discovered, which makes the absence of a control the obvious gap. Why this is a small slice once writes exist: - Models is map[string]string, addressed by the whole dotted key "models", exactly the shape that made Repos writable in archie-core-b6ew.6 via UpdateConfig(ctx, {"repos": repos}). No array-index overlay support needed. - Models is already in reloadableFields (internal/app/archied/reload.go:147), and ForTask rebuilds the per-task snapshot from d.Cfg.Get() at dispatch, so a write takes effect on the next task with no restart. - The candidate values are already computed: applyModelCatalog returns the sorted provider/model refs as b.catalogModels, and cfg.Providers is merged with everything the catalog discovered, so the picker has its options without new discovery. - config_schema.go currently marks models FieldStructured/Editable:false. Scope: role -> model ref only. Not adding or removing providers, not editing credentials, not chat.models. Blocked by archie-core-j28m: the UI process has no write path at all (UpdateConfig/ResetConfig/UpdateRepoField are nil in production and compose_test.go asserts they stay nil), so this cannot land until that bead picks a transport. Acceptance: changing builder from one provider/model to another in the dashboard persists, republishes the snapshot so the page does not show the operator their own edit missing, and the next dispatched task uses it without a daemon restart. An unknown model ref is rejected before persist. ### Close reason Closed --- _Imported from beads `archie-core-1786637498420-327-bacadaae.1` · GitHub #941 · type task · priority P2 · created 2026-09-18 · closed 2026-10-05_
sam added the mediumtask labels 2026-10-27 13:38:03 +00:00
sam self-assigned this 2026-10-27 13:38:03 +00:00
sam closed this issue 2026-10-27 13:38:03 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sam/archie#860