Plugin directory / Developer / dsh-oai-oauth
dsh-oai-oauth
Verified · install-tested on dsh werifu
What it does
A plugin allowing you to use ChatGPT via OpenAI subscription without API Key in Deepseek Harness
Works — verified, early-stage project
A plugin allowing you to use ChatGPT via OpenAI subscription without API Key in Deepseek Harness It installs cleanly and boots without issues in our testing. It's early-stage but functional.
“Verified” means our automated CI actually ran dsh plugin add in a clean profile and it booted — nothing more. Feature descriptions and version compatibility are the author’s claims. This is not a security audit and not an endorsement of third-party code.
README
dsh-oai-oauth
A DeepSeek Harness (DSH) LLM adapter that uses your OpenAI ChatGPT subscription (OAuth) without API KEY. It reuses your local Codex CLI login (~/.codex/auth.json).

Install
dsh plugin --profile web add dsh-oai-oauth
Usage
dsh web
Then open Settings → Models, pick OpenAI ChatGPT (OAuth), and log in with your ChatGPT account.
Uninstall
dsh plugin --profile web remove dsh-oai-oauth
License
MIT
Install
Install the catalog once, then DeepSeek Harness can find and install any plugin from this site automatically:
dsh plugin add dshbase-catalog Then say "install dsh-oai-oauth for me" — your agent finds it in the directory and installs it. Docs: dshbase-catalog · verified packs.
Web profile:
dsh plugin --profile web add dsh-oai-oauth Headless (CLI) profile:
dsh plugin --profile headless add dsh-oai-oauth Package
npm: dsh-oai-oauth · version 0.1.0 · tested on dsh 0.1.0-rc.6
Test report
Verified end-to-end: L1 install + L2 load + L3 runtime Q&A on dsh 0.1.0-rc.6.
When to use it
Extend the agent's coding surface — give it a new tool, workflow, or integration so it handles a dev task it couldn't before.
Who it's for
Developers who want dsh to behave like a teammate on real codebases — editing, running, and verifying changes rather than just answering.
For developers — extending it
The tool/command surface is the seam: expose more of the SDK, add smarter context wiring, or tighten the loop between code changes and verification.