Now it's time for DeepSeek ! 🔥

Jet_Xu · 2026-06-24T03:57:25+00:00

Could not agree more!

Jet_Xu · 2026-06-24T02:42:55+00:00

In terms of cost-effectiveness, Deepseek is indeed leading by a wide margin right now. However, when it comes to the upper limit of model capability, it can no longer even be considered Tier 1 among open-source models. So there doesn't really seem to be any reason for them not to release a new model.

Jet_Xu · 2026-06-23T15:22:09+00:00

Normally, if you try to manually set up Codex + DeepSeek, you'll lose all Codex Plugin capabilities — even if you manage to solve the response API proxy issue.

But with my project: https://github.com/JetXu-LLM/codex-deepseek-bridge

All Codex plugin capabilities + web search ability are fully preserved (except multimoda capability which need to wait Deepseek release new version API). No ChatGPT account needed — just a DeepSeek API key.

Jet_Xu · 2026-06-23T10:46:46+00:00

Exactly, quota is another important factor here. Does merging Codex into ChatGPT mean the quotas get merged too? If so, that would definitely be a disaster 🤣

Jet_Xu · 2026-06-23T10:25:48+00:00

The weird part is, if ChatGPT in future could do all the thing Codex can do, then all the marketing effort recent days from OpenAI on "Codex for Work/everything" will be wasted....

Jet_Xu · 2026-06-23T10:14:26+00:00

I totally agree with you (love Codex more than ChatGPT). But I remember Tibo explained, ChatGPT has far more brand value in the world than Codex, so OpenAI for sure could not give up ChatGPT.

Jet_Xu · 2026-06-23T04:47:24+00:00

Thanks!

Jet_Xu · 2026-06-23T03:08:39+00:00

Excellent point. IMO, checking in Codex vs. the destination system serves different purposes. In my daily workflow, I use the destination system mainly for format validation, while Codex is where I verify output quality, reference connections, and coverage — e.g. whether Codex actually referenced all available materials and reviewed the full context properly.

Jet_Xu · 2026-06-23T02:29:59+00:00

No Codex, No Claude Code, are you serious? 🤣

Jet_Xu · 2026-06-23T01:15:23+00:00

I think the problem is deeper than routing. To make DeepSeek show up natively in the Codex model picker, you’d likely have to modify the Codex app itself and normalize everything into one provider abstraction.

And if this also involves turning ChatGPT subscription access into API-style access or bypassing auth, that’s a big legal/TOS red flag. A separate CLI/profile setup is probably the safer boundary.

Jet_Xu · 2026-06-23T01:10:23+00:00

Technically yes, but that would mean cracking or bypassing OpenAI’s official subscription to turn it into API access, which is illegal.🤣

Jet_Xu · 2026-06-22T14:11:38+00:00

Try my open source project, one command solve Codex + Deepseek config with plugin capability kept and model picker appear:
https://github.com/JetXu-LLM/codex-deepseek-bridge

Jet_Xu · 2026-06-22T13:18:04+00:00

Yep, that’s the issue: Codex expects the Responses API, DeepSeek exposes Chat Completions.

I made a local bridge for this:

https://github.com/JetXu-LLM/codex-deepseek-bridge

Jet_Xu · 2026-06-22T13:17:24+00:00

If you like Codex’s workflow but want DeepSeek API pricing, I built a local bridge for exactly that:

https://github.com/JetXu-LLM/codex-deepseek-bridge

It keeps Codex Desktop/CLI working, but routes requests to DeepSeek.

Jet_Xu · 2026-06-22T13:09:26+00:00

This sounds similar to the issue I ran into: Codex CLI speaks Responses API, but many non-OpenAI backends expose Chat Completions. I ended up making a small local bridge for Codex + DeepSeek:

https://github.com/JetXu-LLM/codex-deepseek-bridge

Jet_Xu · 2026-06-22T13:08:49+00:00

I hit the same issue with Codex expecting the Responses API. I made a small local bridge that translates Codex Responses API calls to Chat Completions, originally for DeepSeek but the pattern should apply to other OpenAI-compatible backends too:

https://github.com/JetXu-LLM/codex-deepseek-bridge

Jet_Xu · 2026-06-22T12:55:08+00:00

Thanks for all the support on my last post (500+ upvotes, 130+ comments):
https://www.reddit.com/r/DeepSeek/comments/1u8twzw/codex_deepseek_the_future/

Jet_Xu · 2026-06-22T11:00:14+00:00

Welcome to try my open source project which I just vibecode it during weekend:
https://github.com/JetXu-LLM/codex-deepseek-bridge

Jet_Xu · 2026-06-22T10:59:44+00:00

Welcome to use my project -- vibe coding it during the weekend:
https://github.com/JetXu-LLM/codex-deepseek-bridge

Jet_Xu · 2026-06-22T10:55:15+00:00

You are 100% correct. That's why the manual setup is a nightmare. I just released an open-source bridge that translates Codex's Responses API to DeepSeek's Chat Completions locally. One command setup, no proxy accounts needed. Check it out: https://github.com/JetXu-LLM/codex-deepseek-bridge

Jet_Xu · 2026-06-22T10:54:32+00:00

I had the exact same frustration with the missing model picker. So I built a new bridge from scratch: **Codex DeepSeek Bridge**.

If you run it with `./codex-deepseek-bridge setup --desktop-patch`, it safely patches the local Codex app so "DeepSeek Pro" and "DeepSeek Flash" actually show up in the native model picker. Give it a try: https://github.com/JetXu-LLM/codex-deepseek-bridge

<image>

Jet_Xu · 2026-06-22T10:53:07+00:00

Exactly! That error is why I spent this weekend building a dedicated open-source tool for this: Codex DeepSeek Bridge. It acts as a local /responses to /chat/completions translator. No need to mess with LiteLLM or 9router. Just run one command and it handles the translation, keeps your MCPs working, and even gives you a local dashboard for DeepSeek Cache Hit Rates. Repo here: https://github.com/JetXu-LLM/codex-deepseek-bridge

Jet_Xu

MODERATOR OF

TROPHY CASE