Skip to content

🐛 Copilot-spelled claude-sonnet-5.5 carried onto claude-backend agents and hidden by the model dropdown #19169

Closed

Description

@clubanderson

Problem

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

  1. 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.
  2. 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.
  3. 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.

Activity

  1. added
    help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
    on Nov 18, 2026
  2. added 2 commits that reference this issue on Nov 18, 2026
    9b214cc
    6fa7c42
  3. clubanderson commented on Nov 18, 2026

    @clubanderson
    MemberAuthor

    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.

  4. added a commit that references this issue on Nov 19, 2026
    37b0f4a
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    has-open-prhelp wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.triage/acceptedIndicates an issue or PR is ready to be actively worked on.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions