You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
🐛 Copilot-spelled claude-sonnet-5.5 carried onto claude-backend agents and hidden by the model dropdown #19169
Five claude-backend agents on a hosted hive were configured with model: claude-sonnet-5.5 (the Copilot spelling). The Claude CLI rejects that id, so every kick failed with "There's an issue with the selected model (claude-sonnet-5.5)". The Claude CLI id is claude-sonnet-5-5.
The owner could not see the problem: the agent's model dropdown showed claude-sonnet-5-5 as selected while the stored value (and the details grid) said claude-sonnet-5.5. This has happened before.
Root cause
POST /api/switch/{agent}/{backend} (handleSwitch, src/pkg/dashboard/api_agent_control.go) changes only the backend. The audit log shows the agents ran on copilot with claude-sonnet-5.5 (valid there) and were switched to claude on 2026-11-18; the copilot-spelled model was carried over unchanged.
The dropdown's preselect uses _modelIdMatches (src/pkg/dashboard/static-src/js/backends-tokens.js), which folds dotted and dashed versions together (_modelsEqual). A stored claude-sonnet-5.5 preselects the claude-sonnet-5-5 option, so the invalid value is hidden. The same tolerant match makes model auto-heal treat it as available, so it is never repaired.
Nothing normalizes the id for claude: normalizeModelNameForBackend (src/crux/agent/manager_routing.go) passes claude models through verbatim, the config loader accepts it, and PUT /api/config/agent/{name}/models stores it as sent.
Fix
config.CanonicalizeClaudeModel: unprefixed claude-* ids with dots become dashed (claude-sonnet-5.5 to claude-sonnet-5-5); aliases, dashed ids and gateway ids (anthropic/...) are untouched.
Applied on the backend switch to claude, /api/model, PUT .../models, config load (with a per-agent dashboard warning and an overlay rewrite), the served claude model list, and at launch.
The claude dropdown no longer folds spellings: a stored dotted id is shown as stored and flagged "not valid for claude; pick claude-sonnet-5-5". The UI shows the server's warning after a switch.
Scope extended: the same models have different naming conventions on the claude and copilot backends, so the fix in #19170 now works both ways through one shared mapping (claude-sonnet-5.5 to claude-sonnet-5-5 on claude, claude-sonnet-5-5 to claude-sonnet-5.5 on copilot), and both model dropdowns show and flag a wrong-convention stored id. Non-Claude Copilot ids pass through.
Activity
🐛 Fix config test literal and refresh api-reference citations
🐛 Normalize Claude model ids both ways between claude and copilot
clubanderson commentedon Nov 18, 2026
Scope extended: the same models have different naming conventions on the claude and copilot backends, so the fix in #19170 now works both ways through one shared mapping (claude-sonnet-5.5 to claude-sonnet-5-5 on claude, claude-sonnet-5-5 to claude-sonnet-5.5 on copilot), and both model dropdowns show and flag a wrong-convention stored id. Non-Claude Copilot ids pass through.
🐛 Normalize Claude model ids both ways between the claude and copilot…