Summary
The Anthropic provider seed declares claude-sonnet-5 as the default model, but the Workbench UI displays claude-fable-5 as the default after a fresh setup and seed.
Reproduction
- Start Workbench with an Anthropic API key configured.
- Run
bun run setup and bun run seed.
- Open Settings → Connections.
- Observe the Default model value.
The seeded Anthropic catalog contains multiple offerings, and the UI shows claude-fable-5.
Expected behavior
The UI should reflect the declared Anthropic default (claude-sonnet-5) or the product should explicitly define a different default policy.
Observed behavior
The UI derives the current model from the first offering after sorting by priority and canonical name. Seeded offerings currently share priority 0, so alphabetical ordering puts claude-fable-5 first.
Relevant code:
apps/hub/src/config.ts: SEED_MODEL = "claude-sonnet-5"packages/cli/src/config.ts: DEFAULT_MODEL = "claude-sonnet-5"packages/settings-ui/src/connections-section.tsx: selects ordered[0]packages/inference-settings/src/effective-list.ts: equal-priority tie-break sorts by canonical name
Impact
The configured provider default and the visible/runtime Workbench default can disagree. It also makes the selected model surprising for cost-sensitive testing, where Haiku may be intended.
Suggested direction
Seed explicit offering priorities (or otherwise persist the intended default) so the UI and runtime resolver agree. Add a regression test covering a freshly seeded Anthropic catalog.
Summary
The Anthropic provider seed declares
claude-sonnet-5as the default model, but the Workbench UI displaysclaude-fable-5as the default after a fresh setup and seed.Reproduction
bun run setupandbun run seed.The seeded Anthropic catalog contains multiple offerings, and the UI shows
claude-fable-5.Expected behavior
The UI should reflect the declared Anthropic default (
claude-sonnet-5) or the product should explicitly define a different default policy.Observed behavior
The UI derives the current model from the first offering after sorting by priority and canonical name. Seeded offerings currently share priority
0, so alphabetical ordering putsclaude-fable-5first.Relevant code:
apps/hub/src/config.ts:SEED_MODEL = "claude-sonnet-5"packages/cli/src/config.ts:DEFAULT_MODEL = "claude-sonnet-5"packages/settings-ui/src/connections-section.tsx: selectsordered[0]packages/inference-settings/src/effective-list.ts: equal-priority tie-break sorts by canonical nameImpact
The configured provider default and the visible/runtime Workbench default can disagree. It also makes the selected model surprising for cost-sensitive testing, where Haiku may be intended.
Suggested direction
Seed explicit offering priorities (or otherwise persist the intended default) so the UI and runtime resolver agree. Add a regression test covering a freshly seeded Anthropic catalog.