Codex Desktop with third-party APIs while keeping plugin/account compatibility #6
Replies: 2 comments 7 replies
-
|
这个项目做的非常好。从 0.9.0 开始使用的。 |
Beta Was this translation helpful? Give feedback.
-
|
This is a very useful direction for Codex Desktop users. Keeping the official OpenAI-authenticated provider path while routing the actual model backend to DeepSeek / MiMo / Kimi / GLM is much more valuable than just making Codex call another OpenAI-compatible endpoint. For real coding workflows, I think the key things to compare are:
I’m especially interested in the DeepSeek / BytePlus / China-model API side for indie devs and small AI teams. This kind of gateway approach seems very relevant for lower-cost coding workflows. Happy to test or exchange notes if useful — are you mainly looking for feedback on DeepSeek setup, provider compatibility, or Codex Desktop plugin/account behavior? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
AgentGate is a local AI gateway for coding agents. The newest documentation pass highlights a capability that is easy to miss but important for Codex Desktop users:
Codex Desktop can use third-party APIs such as DeepSeek and Xiaomi MiMo while keeping the official OpenAI-authenticated provider path that plugin and account features expect.
Why this matters
Many local proxies make Codex behave like a generic OpenAI-compatible client. That can be enough for plain model calls, but Codex Desktop also has account, provider, and plugin assumptions tied to its official OpenAI provider path.
AgentGate keeps that shape:
The goal is not just "make Codex call another model". The goal is to let users switch model backends while preserving as much of the native Codex Desktop experience as possible.
Useful docs
Feedback wanted
If you use Codex Desktop with DeepSeek, MiMo, Kimi, GLM, DashScope, or another third-party provider, I would love to know:
Beta Was this translation helpful? Give feedback.
All reactions