DSH 插件市场DeepSeek Harness 社区插件目录

dsh-coding-subscription-oauth

已验证 开发与运维 ★ 28 0.8.7

DeepSeek Harness coding-subscription OAuth: SuperGrok/Grok Build, ChatGPT Plus Codex, Kimi Code, Claude Code. Fixes AUTH API key is invalid, INVALID_REPLAY_STATE, grok-4.6 xhigh, Kimi Bearer vs x-api-key.

一句话定位

DeepSeek Harness coding-subscription OAuth: SuperGrok/Grok Build, ChatGPT Plus Codex, Kimi Code, Claude Code. Fixes AUTH API key is invalid, INVALID_REPLAY_STATE, grok-4.6 xhigh, Kimi Bearer vs x-api-key.

安装方式

在 DSH 的 web profile 中执行下面的命令;装完刷新页面即可。

$ dsh plugin --profile web add dsh-coding-subscription-oauth@0.8.7

兼容的 DSH 版本

>=0.1.1-rc.2 <0.3.0

作者与热度

lninghaha · ★ 28 · 更新于 2026-10-23

关于这个插件

🔐 dsh-coding-subscription-oauth

v0.8.7 · formerly dsh-grok-build

Coding-subscription OAuth for DeepSeek Harness. Use SuperGrok / X Premium (Grok Build), ChatGPT Plus/Pro (Codex), Kimi Code, Claude Pro/Max and Google Antigravity inside DSH — without a second API-key bill and without pasting any token into chat.

*English · 中文版 · 日本語 · 한국어 · Português (BR) · Español · Français · Deutsch · Русский* Upgrade / 升级: Follow the versioned steps in INSTALL.md. 0.8.0 adds opt-in OpenCode Go compatibility (sticky x-opencode-session on the local gateway). Current main pins the shared dispatcher runtime on dsh-coding-oauth-core@0.1.2 and undici@7.29.0, and restricts gateway key reveal/rotate to loopback access; no configuration, credential, data, or route migration is required. Grok Imagine retains its explicit pinned dispatcher. Releases from 0.6.2 onward include the strict Cordis injection startup fix and DSH 0.1.1-rc.2 support; keep profile/config/credential files and restart one existing DSH Web process only after updating. Name change

Published first as dsh-grok-build when it only covered Grok Build. The current name matches the full coding-subscription OAuth surface. ✨ Features 🧽 Bring your own subscription — SuperGrok, ChatGPT Plus/Pro, Kimi Code, Claude Pro/Max; no extra pay-as-you-go key. 🔑 Local OAuth, no key-pasting — authorize in Settings or CLI; access/refresh tokens never enter chat, logs or HTTP status. 🧩 One plugin, five providers — Grok Build (cli-chat-proxy.grok.com), Codex, Kimi Code, Claude Code and Google Antigravity. 🛡️ Secure by design — credential files are owner-only 0600, atomically written, cross-process locked. ⚙️ Dynamic catalog — the selector lists only signed-in routes, labelled (OAuth), including grok-4.6 xhigh. 🌐 Proxy-aware — proxies only reviewed subscription domains; Kimi China stays direct by default. 📥 Manual CLI Pull — Settings discovers allowlisted official Grok/Codex/Kimi/Claude CLI OAuth files read-only; you pull a one-way copy after preview and overwrite confirmation. 🗂️ Tabbed Settings — Accounts, Gateway, Capabilities, and About; remote hosts prefer device-code sign-in with quieter CLI-missing tips; signed-in cards stay collapsed until expanded. 🎛️

These are the searches and DSH errors that usually lead here. If one of them is your tab title, you are in the right repo. Grok Build device login, live /v1/models-v2 and Responses streaming are verified on real deployments. Codex / Kimi / Claude reuse @earendil-works/pi-ai native OAuth instead of re-implementing vendor flows. Supported providers Grok Build's device login, dynamic /v1/models-v2 catalog and Responses streaming are verified on real deployments. Codex/Kimi/Claude reuse the provider-native OAuth/refresh from @earendil-works/pi-ai instead of re-implementing vendor flows. 🚀 Qu

相似插件