docs: add Codex DeepSeek Bridge guide#265
Open
JetXu-LLM wants to merge 2 commits into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
setupcommand, paste a DeepSeek API key, then restart Codex.restoreremoves the managed config.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
Documentation
docs/assets/with descriptive filenames and reasonable sizes