Skip to content

fix(workbuddy): stop rewriting deepseek-v4.1-flash to deep-model - #163

Merged
caigee-cmd merged 1 commit into
mainfrom
fix/workbuddy-deepseek-native-id
Sep 15, 2026
Merged

caigee-cmd merged 1 commit into
mainfrom
fix/workbuddy-deepseek-native-id

Conversation

@caigee-cmd

Copy link
Copy Markdown
Owner

Summary

  • WorkBuddy chat no longer hardcodes deepseek-v4.1-flashdeep-model when building the upstream request.
  • Upstream model IDs now come from the live catalog native spelling; legacy deep-model catalogs still work via the alias entry.
  • This fixes production streaming where requested deepseek-v4.1-flash silently came back as kimi-k3 / glm-5.3.

Test plan

  • go test ./internal/providers/workbuddy -count=1
  • After deploy on us1, stream deepseek-v4.1-flash and confirm chunk model stays deepseek-v4.1-flash (or at least not kimi-k3/glm-5.3)
  • Confirm request_logs.mapped_model for the stream request is no longer a random fallback model
  • Optional: console account/model refresh after recreate, then recheck /v1/models shows native_model=deepseek-v4.1-flash

Current WorkBuddy catalogs already expose deepseek-v4.1-flash natively.
The hardcoded alias sent deep-model upstream and let chat silently fall
back to other models. Resolve the upstream ID from the live catalog
instead, keeping the legacy deep-model path only when the catalog still
publishes that native spelling.
@caigee-cmd
caigee-cmd merged commit e77817f into main Sep 15, 2026
6 checks passed
@caigee-cmd
caigee-cmd deleted the fix/workbuddy-deepseek-native-id branch September 15, 2026 15:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant