Telegram model picker drops mixed-case provider slugs
NousResearch/hermes-agent · cluster 35932 · gateway
Data as of
6 open items. Fix attempted, not merged.
The short answer
2open issues
4open PRs
7items grouped
- Known?
- Yes. 7 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
- 2 issues and 4 PRs.
Next step: read the attempts below. Your case may extend or revive that work.
Pick up a Lab taskThese issues and fixes address a bug where the Telegram /model picker silently omits user-defined providers whose slugs contain mixed-case characters, due to case-sensitive slug lookup logic. The fixes apply case normalization to ensure such providers are included correctly.
Open issues2
Open PRs4
- PR#35933fix: normalize provider slug case in Telegram model picker keyboard
- PR#35953fix: preserve mixed-case providers in Telegram model picker
- PR#37282fix(telegram): use case-insensitive slug lookup in model picker
- PR#138775fix(telegram): normalize slug case in _build_provider_keyboard (active plugin path)
1 PR closed without merging
From the close comments: other 1
-
#71920 fix(telegram): normalize provider slug case in /model picker keyboard (#35932) · other →
#35932,#35933
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.30: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means 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 LabAt a glance
- Subsystem
- gateway
- Closed issues
- 0
- Attempts
- 1 PR closed without merging