[PR #265] [CLOSED] docs: add Codex DeepSeek Bridge guide #298

Closed
opened 2026-10-26 09:47:45 +00:00 by bsakaguchi · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/deepseek-ai/awesome-deepseek-agent/pull/265
Author: @JetXu-LLM
Created: 6/28/2026
Status: ❌ Closed

Base: main ← Head: codex/add-codex-deepseek-bridge-guide


📝 Commits (2)

  • b9f63ca docs: add Codex DeepSeek Bridge guide
  • 01a3bfb docs: streamline Codex DeepSeek Bridge guide

📊 Changes

5 files changed (+226 additions, -0 deletions)

View changed files

➕ docs/assets/codex_deepseek_bridge_composer.png (+0 -0)
➕ docs/assets/codex_deepseek_bridge_picker.jpg (+0 -0)
➕ docs/assets/codex_deepseek_bridge_report.png (+0 -0)
➕ docs/codex_deepseek_bridge.md (+113 -0)
➕ docs/codex_deepseek_bridge.zh-CN.md (+113 -0)

📄 Description

Summary

  • Add a bilingual Codex App guide for Codex DeepSeek Bridge.
  • Focus on the simple path: download the bridge, run one setup command, paste a DeepSeek API key, then restart Codex.
  • Highlight the user-facing benefits up front: no ChatGPT subscription, local key storage, Codex approvals/plugins/MCP/tools stay in the Codex workflow, and restore removes the managed config.
  • Include screenshots for the Codex composer, local report, and optional Desktop model picker labels.

Why

Codex uses the Responses API, while DeepSeek currently exposes Chat Completions. Codex DeepSeek Bridge provides a packaged local bridge so users can keep the official Codex app and route model calls to DeepSeek V4.

I intentionally did not add a new README table row because the README already has a top-level Codex entry. This is a Codex-specific supplemental bridge guide rather than a separate top-level agent entry. Happy to add an index link or table row if maintainers prefer that structure.

Related: #245, #198. This PR does not close either issue: #245 asks for native DeepSeek Responses API compatibility, while this guide documents a local bridge path; #198 reports model-list visibility for the existing Codex guide, while this guide keeps the default app setup simple and treats full Desktop picker labels as optional.

See CONTRIBUTING.md for full guidelines.

Checklist

Agent Configuration

  • Model names are current (v4-pro / v4-flash, not v3 names)
  • 1M context is configured or mentioned
  • Max thinking effort level is supported
  • Pricing: not included in this guide
  • Config fields are verified against the current Codex DeepSeek Bridge docs/code
  • No workarounds for already-fixed upstream bugs

Documentation

  • Both English and Chinese versions included in a single PR
  • README table entry: intentionally unchanged because README already has a top-level Codex entry
  • One tool per PR; unrelated tools not combined
  • Images placed in docs/assets/ with descriptive filenames and reasonable sizes

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/deepseek-ai/awesome-deepseek-agent/pull/265 **Author:** [@JetXu-LLM](https://github.com/JetXu-LLM) **Created:** 6/28/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `codex/add-codex-deepseek-bridge-guide` --- ### 📝 Commits (2) - [`b9f63ca`](https://github.com/deepseek-ai/awesome-deepseek-agent/commit/b9f63cac4d3a2d22f2a727287bcb43223e3ceef1) docs: add Codex DeepSeek Bridge guide - [`01a3bfb`](https://github.com/deepseek-ai/awesome-deepseek-agent/commit/01a3bfb4eb7f80919a69540e2668675624325cf3) docs: streamline Codex DeepSeek Bridge guide ### 📊 Changes **5 files changed** (+226 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `docs/assets/codex_deepseek_bridge_composer.png` (+0 -0) ➕ `docs/assets/codex_deepseek_bridge_picker.jpg` (+0 -0) ➕ `docs/assets/codex_deepseek_bridge_report.png` (+0 -0) ➕ `docs/codex_deepseek_bridge.md` (+113 -0) ➕ `docs/codex_deepseek_bridge.zh-CN.md` (+113 -0) </details> ### 📄 Description ## Summary - Add a bilingual Codex App guide for **Codex DeepSeek Bridge**. - Focus on the simple path: download the bridge, run one `setup` command, paste a DeepSeek API key, then restart Codex. - Highlight the user-facing benefits up front: no ChatGPT subscription, local key storage, Codex approvals/plugins/MCP/tools stay in the Codex workflow, and `restore` removes the managed config. - Include screenshots for the Codex composer, local report, and optional Desktop model picker labels. ## Why Codex uses the Responses API, while DeepSeek currently exposes Chat Completions. Codex DeepSeek Bridge provides a packaged local bridge so users can keep the official Codex app and route model calls to DeepSeek V4. I intentionally did not add a new README table row because the README already has a top-level **Codex** entry. This is a Codex-specific supplemental bridge guide rather than a separate top-level agent entry. Happy to add an index link or table row if maintainers prefer that structure. Related: #245, #198. This PR does not close either issue: #245 asks for native DeepSeek Responses API compatibility, while this guide documents a local bridge path; #198 reports model-list visibility for the existing Codex guide, while this guide keeps the default app setup simple and treats full Desktop picker labels as optional. See [CONTRIBUTING.md](./CONTRIBUTING.md) for full guidelines. ## Checklist ### Agent Configuration - [x] Model names are current (v4-pro / v4-flash, not v3 names) - [x] 1M context is configured or mentioned - [x] Max thinking effort level is supported - [x] Pricing: not included in this guide - [x] Config fields are verified against the current Codex DeepSeek Bridge docs/code - [x] No workarounds for already-fixed upstream bugs ### Documentation - [x] Both English and Chinese versions included in a single PR - [x] README table entry: intentionally unchanged because README already has a top-level Codex entry - [x] One tool per PR; unrelated tools not combined - [x] Images placed in `docs/assets/` with descriptive filenames and reasonable sizes --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
bsakaguchi 2026-10-26 09:47:45 +00:00
Sign in to join this conversation.
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
deepseek-ai/awesome-deepseek-agent#298
No description provided.