Issue Station
Sign In
Tools hereToolbox

hermes - 💡(How to fix) Fix DeepSeek provider picker description still lists old V3/R1/coder models [3 pull requests]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Fix Action

Fixed

RAW_BUFFERClick to expand / collapse

The provider selection menu currently shows DeepSeek as:DeepSeek (DeepSeek-V3, R1, coder — direct API) This is stale now that the direct DeepSeek provider exposes the first-class V4 models, including deepseek-v4-pro and deepseek-v4-flash. The model list already includes those IDs, but the provider-level description makes the active provider look outdated or incorrectly configured. Expected: the provider picker should mention DeepSeek V4 Pro / V4 Flash instead of the older V3/R1/coder wording. Observed in the terminal provider picker: DeepSeek (DeepSeek-V3, R1, coder — direct API)

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#optimization#mixed precision#training loop#device allocation

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING