DeepSeek Harness Plugin Hub

发布与管理完整 Harness Profiles,发现适合你的插件。

探索

插件目录环境预设文档中心动态

社区

发布插件联系我们报告问题

相关链接

Plugin Hub GitHubDeepSeek Harness 官方项目系统状态隐私说明
© 2026 DeepSeek Harness Plugin HubPowered byPaxTech

独立、非官方社区项目,与 DeepSeek 官方无隶属、授权或背书关系。

Openai Account Connector — DeepSeek Harness 插件(DSH Plugin)
DeepSeek Harness Plugin Hub
ProfilesPlugins分类动态文档登录管理 Profiles
ProfilesPlugins分类动态文档登录
← Plugins
O

dsh-openai-account-connector

Openai Account Connector

用于 DeepSeek Harness 的社区 OpenAI 账户模型连接器

插件会安装到这里;不确定时保持 web。

npx -y @deepseek-ai/dsh plugin --profile web add github:lxy271713/dsh-openai-account-connector#a985e609ae433b66852ef5bbcb9fb488f7b9ea19
README兼容性版本

兼容性与来源证明

Openai Account Connector 以 dsh-openai-account-connector 发布,当前版本为 0.1.4。Plugin Hub 会校验它的 manifest,并保存精确安装来源,便于复现安装结果。

DSH 兼容范围
*
运行环境
any
发布来源
github
Registry 更新时间
2026/9/21

版本

0.1.4stable
2026/9/21

相关插件

正在加载相关插件…

最新版
0.1.4
DSH
*
HMR
重启进程
Tree shaking
未声明可安全裁剪
解包体积
未提供
文件数
未提供
Surface
any
许可证
MIT
发布源
github
GitHub
★ 0
周下载
0
最近提交
2026/9/21
查看源码 ↗
README Badge

点击下方 Badge 复制 Markdown,粘贴到 README 即可。

这是你的 Plugin?认领权益 · 优先安全扫描

验证 package.json 声明的 GitHub 仓库,即可管理这个公开页面。认领后,Hub 会优先安排当前版本的安全扫描,并在通过后公开展示结果。

认领这个 Plugin →
报告问题

相关插件

继续浏览 models-usage 分类下经过校验的插件。

Usage@linxin666/dsh-usage用于 dsh Web GUI 的使用统计插件:检测各提供商的余额和编程套餐配额,并实时记录令牌使用情况;侧边栏 Settings 行上方显示紧凑的价格概览卡片Whale Widgetdsh-whale-widgetDSH Web 界面右下角的 DeepSeek 余额小鲸鱼挂件:余额/今日已用/峰谷定价、自定义泡泡点击序列(文本/余额/今日/峰谷/图片/随机语句与并列加权选择)、逐行样式与字体、悬浮快捷编辑、音效与每轮消耗、自定义角色/动图/音效、吸附与翻转自定义Commandcode Provider@mars-sea/dsh-commandcode-provider适用于 Command Code 的非官方 DeepSeek Harness LLM 提供商插件,移植自 pi-commandcode-provider(MIT)。注册“commandcode”提供商路由,并在 Models 页面添加卡片和实时模型目录。Plugin Subscriptionsdsh-plugin-subscriptions将 ChatGPT (Codex)、Claude、Grok (X Premium)、GitHub Copilot 和 Google Antigravity 订阅用作 DeepSeek Harness LLM 提供商,并通过网页设置页面使用 OAuth 登录

README

DSH OpenAI Account Connector

dsh-openai-account-connector connects official OpenAI account sign-in, the live GPT model catalog, and image generation to DeepSeek Harness's single model directory. The user signs in only on the official OpenAI browser page. The plugin has no token input and never reads, copies, logs, or returns an OAuth token.

After connection, the Connector registers the openai-codex route in ctx.llm. The native DSH composer lists the app-server model catalog and receives text or durable Harness image blocks from the same selected route. Generated files pass path-containment, symlink, file-type, and byte-limit checks before entering the Harness attachment store.

Requirements and installation

This release supports formal DSH Desktop 2.0.3 when dsh-account-authorization@0.1.0 supplies the target-preserving authorization compatibility layer. Later Harness builds may provide the same contract natively through the authorization-target work after commit 732a504. llm-pi-ai.delegatedProviders is also required. Install the Provider-neutral account surface once, then install this Provider-specific Connector:

dsh plugin --profile desktop add --save-exact dsh-account-authorization@0.1.0
dsh plugin --profile desktop add --save-exact dsh-openai-account-connector@0.1.4

The connector includes a tested Codex runtime, so users only need to complete the OpenAI browser login. Model choices are refreshed from that runtime on every model-list request. Advanced installations may still set CODEX_BIN or the plugin's executable option to use a system Codex CLI.

Updating the connector updates its compatible Codex runtime; it does not grant models that OpenAI has not enabled for the signed-in account. Image generation is exposed as a live account capability and may not appear as a separate selectable model.

The account-surface bundle owns the Harness authorization registry and shared UI. This Connector bundle owns only the OpenAI flow and adapter, and assigns openai-codex to that adapter so the generic pi-ai adapter and this adapter never own the same route. Removing this Connector therefore cannot remove another Provider's account surface.

Security and state ownership

  • Codex app-server exclusively owns ChatGPT OAuth storage and refresh.
  • Harness credentials store only a non-secret connected marker.
  • Harness ctx.llm remains the only Provider/model directory.
  • Harness attachments own generated image bytes and replay references.
  • Each request runs in a new temporary execution workspace; generated images are imported only from the official runtime's declared generated_images root, so the Connector does not grant implicit writes to the user's project.
  • DSH native tool schemas are exposed as app-server dynamic tools; calls return to the Harness agent loop for execution under the selected DSH permission policy.
  • Disconnecting removes only the DSH connection and route. It does not sign the user out of other Codex clients.

Verification

pnpm install
pnpm typecheck
pnpm test
pnpm build
pnpm pack:check

Unit tests are not release evidence. Publication requires a real DSH Desktop 2.0.3 window proving connection, live model refresh, a short text turn, generated image preview, restart replay, and route removal after disconnect.

Known limitations

The app-server image completion item and dynamic-tool protocol are experimental, so the Connector probes live image capability and fails closed on protocol drift. The app-server protocol does not expose DSH's temperature, maxTokens, or stop controls; requests that set them, including auxiliary title requests, fail explicitly instead of parsing Harness-owned title prompts or silently ignoring controls. Image turns publish the first completed image only after the runtime confirms the turn was interrupted. Because app-server does not expose a stable image-creation id, whole-turn retries are disabled for this Provider route, including text requests; transient failures therefore surface to the user instead of being retried. Harness attachments currently have no staging transaction; cancellation immediately after a successful attachment save may leave one unreferenced content-addressed object for the attachment retention policy. Additional Providers require independent Connector packages rather than branches in this UI or in Harness core.