Skip to content

Generalize DeepSeek provider for any OpenAI-compatible API#76

Merged
pescheck-bram merged 2 commits intomainfrom
feature_changed-deepseek-to-generic
Feb 16, 2026
Merged

Generalize DeepSeek provider for any OpenAI-compatible API#76
pescheck-bram merged 2 commits intomainfrom
feature_changed-deepseek-to-generic

Conversation

@pescheck-bram
Copy link
Copy Markdown
Contributor

DeepSeek was already using the OpenAI-compatible API format, but users didn't know they could use it for other providers (LM Studio, z.ai, Groq, etc.). This PR makes it explicit and discoverable.

What Changed

  • Renamed internal implementation to OpenAICompatibleProvider
  • Added openai_compatible provider option alongside deepseek
  • Added --openai-compatible-key and --openai-compatible-base-url arguments
  • Full backward compatibility: all --deepseek-* arguments still work

Why

Users want to use LM Studio, z.ai, and other OpenAI-compatible APIs but didn't realize they could use the DeepSeek provider. This makes it obvious and well-documented.

Usage

LM Studio:

gpt-po-translator --provider openai_compatible \
  --openai-compatible-key dummy \
  --openai-compatible-base-url http://localhost:1234/v1 \
  --folder ./locales

Any OpenAI-compatible API:
gpt-po-translator --provider openai_compatible \
  --openai-compatible-key YOUR_KEY \
  --openai-compatible-base-url https://api.provider.com/v1 \
  --folder ./locales

DeepSeek (unchanged):
gpt-po-translator --provider deepseek \
  --deepseek-key sk-xxx \
  --folder ./locales

Closes #75

@pescheck-bram pescheck-bram merged commit c815b30 into main Feb 16, 2026
17 checks passed
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