DeepSeek Harness Plugin Hub

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

探索

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

社区

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

相关链接

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

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

Github Ci — DeepSeek Harness 插件(DSH Plugin)
← Plugins

dsh-github-ci

Github Ci

用于 DeepSeek Harness 的 GitHub Actions CI 管理器:实时流水线仪表板、OAuth 设备流程登录、仓库浏览器、运行日志和 github_ci 代理工具。

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

npx -y @deepseek-ai/dsh plugin --profile web add dsh-github-ci@1.0.0
README兼容性版本

兼容性与来源证明

Github Ci 以 dsh-github-ci 发布,当前版本为 1.0.0。Plugin Hub 会校验它的 manifest,并保存精确安装来源,便于复现安装结果。

DSH 兼容范围
*
运行环境
web
发布来源
npm
Registry 更新时间
2026/9/3

版本

1.0.0stable
2026/9/3

相关插件

正在加载相关插件…

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

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

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

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

认领这个 Plugin →
报告问题
DeepSeek Harness Plugin Hub
ProfilesPlugins分类动态文档登录管理 Profiles
ProfilesPlugins分类动态文档登录

相关插件

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

Web App@deepseek-ai/dsh-web-appdsh 浏览器界面捆绑包:位于 dsh-base 之上的 Web 补丁层,加上运行时粘合插件(提供前端 dist、Web 界面提示符、bash 运行时变量和 URL 行)Sdk Minimal@deepseek-ai/dsh-sdk-minimal独立的最小 SDK 配置包:JSON-RPC、一个 DeepSeek 适配器、持久化 Shell 和 JSONL 会话Sdk App@deepseek-ai/dsh-sdk-appdsh SDK 配置包:基于 dsh-base 提供 stdio JSON-RPC 服务和进程生命周期管理Subagent Codex@deepseek-ai/dsh-subagent-codex基于官方 app-server 协议的一次性 Codex 子代理提供程序

README

dsh-github-ci

GitHub Actions CI manager for DeepSeek Harness — a live pipeline dashboard in the web UI plus a github_ci agent tool.

Features

  • Pipeline dashboard — floating overlay (or Settings page) with pass/failed/running summary, status badges, and per-run actions
  • Sign in two ways — GitHub OAuth device flow (no client secret; needs an OAuth App with Enable Device Flow checked) or a Personal Access Token (repo + workflow scopes)
  • Repo browser — list your own repos (private + org) or search any public user/org, pick from a dropdown
  • Run actions — cancel in-progress runs, rerun failed jobs, open on GitHub
  • Run logs — failed-step detection with log tails, surfaced to the agent
  • github_ci agent tool — the agent can list workflows/runs, inspect jobs, pull log tails, trigger workflows, cancel and rerun
  • Fix with Agent — one click drafts a structured debug request (run metadata + failure logs) into the chat composer
  • Bad-credential recovery — a rejected token flips the panel back to sign-in with a source-specific explanation (OAuth re-auth vs. paste a new PAT)

Install

dsh plugin --profile web add dsh-github-ci

From source instead:

dsh plugin --profile web add github:knownasmobin/dsh-github-ci

Setup

Option A — OAuth device flow (recommended)

  1. Open GitHub Developer Settings → OAuth Apps → New OAuth App
  2. Name: anything. Homepage / callback URL: http://127.0.0.1:3080
  3. Check "Enable Device Flow" (required — the endpoint returns 404 without it)
  4. Register, copy the Client ID (no secret needed)
  5. Open the panel (⚙ CI in the chat header or sidebar foot) → OAuth tab → paste Client ID → Start OAuth → enter the code at the GitHub activation page

The token is stored in the DSH credential store and reused across sessions.

Option B — Personal Access Token

Generate a token at github.com/settings/tokens with repo and workflow scopes, then paste it in the panel's PAT tab.

No sign-in is required to browse public repositories — anonymous read works out of the box.

Agent tool

github_ci({ action: "list_workflows", owner: "vercel", repo: "next.js" })
github_ci({ action: "get_logs", repo: "owner/repo", run_id: 123456789 })
github_ci({ action: "trigger", owner, repo, workflow_id: "deploy.yml", ref: "main" })

Actions: list_workflows, list_runs, get_run, get_jobs, get_logs, trigger, cancel, rerun.

How it works

  • Host half registers REST routes on the harness web server and the github_ci model tool; GitHub calls go out via fetch with per-request timeouts
  • Client half mounts the dashboard into shell slots (session header, sidebar, overlay, settings) and bridges prompts into the chat composer
  • Credentials live in the DSH credential store — never in the source tree

License

MIT