Codex runs inside DSH while App Server retains authority over model context, tool state and compaction.
DSH integration
Native runtime
Author-claimed
Safety audit
Unaudited
Last verified
2026-10-17
License
MIT
01What can it help you accomplish?
Use Codex without leaving official DSH.
A DSH conversation bound to one persistent Codex App Server Thread.
DSH users who want Codex in the same workspace and conversation interface.
02How to install into DeepSeek Harness
Prerequisites
- Node.js 22.13 or newer and pnpm on PATH.
- Authenticate with an official Codex client before the first session; Codex CLI users can run `codex login`.
Installation steps
- 01
Stop any running DSH Web process before changing the profile bundle.
- 02
Install stable: `npx @deepseek-ai/dsh@0.1.6-alpha.1 plugin --profile web add relay-dsh-plugin-codex@latest`.
$ npx @deepseek-ai/dsh@0.1.6-alpha.1 plugin --profile web add relay-dsh-plugin-codex@latest
- 03
Restart DSH, open New Session, select a workspace and choose Codex before sending the first message.
Verify the integration
- Check that Codex appears in the New Session mode menu, then send a message.
Rollback
- Stop DSH Web, run `dsh plugin --profile web remove relay-dsh-plugin-codex`, then restart.
03DSH integration and capability boundaries
Codex as a native conversation backend in official DSH Web.
Persistent Codex conversation
One App Server Thread per DSH session, with model and reasoning-effort selection and streaming answers.
Host-managed runtime
The DSH Host plugin owns and starts the Codex App Server child process and stops it when DSH or the plugin shuts down.
Starts a Codex App Server child process.
04Who is it for? When not to use it?
Good for
- DSH users who want Codex in the same workspace and conversation interface.
Not for
- Codex App Server remains authoritative for model context, tool state and compaction. DSH stores presentation history and the one-to-one binding.
- Only one App Server can write a Thread. Continuing a thread open in another client may require fully quitting or restarting the owning client.
05Compatibility, maintenance and safety notes
- Codex App Server remains authoritative for model context, tool state and compaction. DSH stores presentation history and the one-to-one binding.
- Only one App Server can write a Thread. Continuing a thread open in another client may require fully quitting or restarting the owning client.
Author README statements; no runtime verification.
06Frequently asked questions
Is Codex authentication still required?
Yes. Authenticate with an official Codex client before the first session; CLI users can run codex login.
Who controls context and compaction?
Codex App Server remains authoritative. DSH keeps presentation history and the durable one-to-one binding.
Can two clients write the same Thread?
No. The App Server protocol allows only one writer for a Thread.
07Related DSH workflows
dsh-our-free-model
by ebony-vinyl
Adds model choices, availability checks, usage panels, and a local OpenAI-compatible forwarder.
dsh-routing-suite
by yjh051108
dsh-routing-suite — injector + router-standard kit: install the runtime injector first, then the task-aware reasoning-mode router preset (measured P1-P23).
dsh-ops
by t-auto
Run Bash and PowerShell commands, search and edit local files, and manage long-running background jobs from DSH.
brooks-lint
by hyhmrright
AI code reviews grounded in 12 classic engineering books — decay risk diagnostics with book citations, severity labels, and 6 analysis modes including full-sweep auto-fix
08Data and sources
`relay-dsh-plugin-codex` adds **Codex as a native conversation backend** to the official [DeepSeek Harness](https://gith…
[](LICENSE)
This page is generated from the project’s public documentation, repository metadata and a structured parse of DSH Plugins; last verified on 2026-10-17. Found an error? Submit a correction.
Best DeepSeek Harness Plugins
Twelve plugins worth installing first — picked from the whole catalog, across every category.