NousResearch/hermes-agent

Stale Alibaba model persisting in token-plan picker

Cluster 119481 · hermes cli. Data as of

2 open items. Fix attempted, not merged.

The short answer

1open issue
1open PR
3items grouped
Known?
Yes. 3 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 1 PR closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
1 issue and 1 PR.

A deprecated Alibaba model ID remains selectable via the token-plan picker because static fallback data re-introduces it after the live catalog omits it, causing 404 errors on selection. These items address removing the stale entry and adjusting catalog resolution logic.

Open issues1

  • Issue#119481[Bug] Stale curated model id (qwen3.8-max-0902) can never age out of the alibaba-token-plan picker — live catalog omits it but the static merge re-adds it; selecting it 404s every turn and silently falls back

Open PRs1

  • PR#126898fix(cli): treat a successful token-plan live catalog as terminal for the model picker

1 PR closed without merging

From the close comments: done elsewhere 1

  • #119489 fix(model): remove stale Alibaba Token Plan model · done elsewhere → #119659, #119489, #110993, #119481
How this cluster was grouped
  • Link evidence (structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
  • Pairwise link density 0.67: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means every pair is linked.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Subsystem
hermes cli
Closed issues
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.