DeepSeek Harness Plugin Hub

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

探索

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

社区

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

相关链接

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

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

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

dsh-autopilot

Autopilot

使用 DeepSeek Harness 将已批准的跟踪器工单转换为可供审查的拉取请求。

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

npx -y @deepseek-ai/dsh plugin --profile web add github:canhta/dsh-autopilot#84a79a89b794fbd5721ef14764afac4423a35b4f
README兼容性版本

兼容性与来源证明

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

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

版本

0.0.0stable
2026/9/11

相关插件

正在加载相关插件…

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

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

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

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

认领这个 Plugin →
报告问题

相关插件

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

Acp App@deepseek-ai/dsh-acp-appdsh ACP 配置文件包:基于 dsh-base 的仅限自动化的 JSON-RPC stdio 和进程生命周期管理Client Ui Task Board@linxin666/dsh-client-ui-task-board面向 DSH Web GUI 的主机权威任务面板,支持实际会话执行、主机 cron 调度以及可选的跨平台空闲睡眠保护;以挂载方式提供,无需修改 DSH 源代码。Web All@linxin666/dsh-web-allDSH Web UI 全家桶聚合插件:一键安装全部功能插件(task-board / git-graph / pet / remote-web-ui / web-ui-settings / skin-center / community-plugins / compat shim)。compat 桥接层已并入本包(src/client),无需独立 compat npm 包。Agent Teams@nanmicoder/dsh-agent-teamsAgentTeams for DeepSeek Harness:通过自然语言驱动多智能体团队协作(队长、成员、具有依赖关系的任务、消息传递),并在 Web GUI 中提供树状监视器

README

dsh-autopilot — Turn tickets into pull requests. Powered by DeepSeek Harness.

dsh-autopilot

dsh-autopilot is an open-source plugin for DeepSeek Harness (DSH). Its goal: move approved tickets from your backlog to review-ready pull requests on your VPS, without supervising every agent turn.

You decide which tickets are ready, when the agent can work and how much it can spend. Autopilot coordinates the work; your repository defines how code is built and checked; people keep control of blockers, review and merge.

Pre-release · bootstrap available. The repository now ships a loadable DSH bundle and its build/test/package workflow. Ticket intake, execution, provider connections and the Web UI are still planned capabilities, not working features. Follow each implementation slice in GitHub Issues.

Product direction · Installation · Local development · Contributing · Documentation

Product direction

  • Work from your existing backlog. Select tickets by a configured label and approved brief. Use Jira or Linear with GitHub or Bitbucket; add providers through Cordis plugins.
  • Control when work starts. Set a schedule, execution limits and spending policy. Eligible work waits in a durable queue until it can run.
  • Pause without losing the workspace. Retain the run, DSH Session and Git worktree so interrupted work can continue.
  • Resolve blockers where the task lives. Receive questions in ticket comments. A human answers and explicitly marks the ticket ready to continue.
  • Stay informed. Configure ticket comments, webhook or ntfy notifications. Manage runs, schedules, budgets and retained worktrees inside DSH Web.
  • Receive a PR ready for human review. The agent follows the target repository's instructions and local checks. Autopilot stops at PR creation; it does not merge or manage remote CI.

How it works

flowchart LR
    accTitle: From approved ticket to review-ready pull request
    accDescr: Approved tickets enter the Autopilot queue. DSH executes eligible work under schedule, capacity and budget limits. Verified local work becomes a review-ready pull request. Notifications are delivered independently after PR creation.

    ticket["Ready ticket<br/>Jira / Linear"]
    queue["Autopilot queue<br/>Schedule + limits"]
    agent["DSH agent<br/>Code + local checks"]
    pr["Review-ready PR<br/>GitHub / Bitbucket"]
    notify["Notify<br/>Configured channels"]

    ticket --> queue --> agent --> pr
    pr -.-> notify

Autopilot selects tickets with the configured ready label and approved Agent Brief, then dispatches eligible work when the schedule, capacity and budget allow. DSH follows the repository's rules in a Git worktree. Creating the verified PR completes the run; notification delivery is independent. Humans own review, merge and marking the ticket Done.

  • Blocked: questions go into ticket comments. A human must reply and mark the ticket ready before work can continue.
  • Paused: keep the Session and worktree. Resume rechecks eligibility and execution limits; an operator pause requires explicit resume.

See run lifecycle for exact pause, recovery and publication rules.

This is an issue-driven AI Development Lifecycle (AIDLC) flow for one project on one VPS. Autopilot adds coordination to DSH; it does not replace the harness's agent runtime, tools or Web application. See product responsibilities for the precise division of ownership.

Installation

The bootstrap can be installed from a locally packed artifact. It does not yet automate tickets, so no Jira, GitHub or model credential is required for this verification path.

Prerequisites: Git, Node.js 24 or newer, and pnpm. DSH itself is invoked from the npm latest tag.

git clone https://github.com/canhta/dsh-autopilot.git
cd dsh-autopilot
pnpm install
mkdir -p .artifacts
pnpm pack --pack-destination .artifacts

npx --yes @deepseek-ai/dsh@latest --profile autopilot --from-default-profile web --dump-config
npx --yes @deepseek-ai/dsh@latest plugin --profile autopilot add ./.artifacts/dsh-autopilot-0.0.0.tgz
npx --yes @deepseek-ai/dsh@latest --profile autopilot --dump-config
npx --yes @deepseek-ai/dsh@latest --profile autopilot --no-open

The third DSH command must show a dsh-autopilot bundle layer containing the autopilot row. DSH prints the local Web URL when the final command boots. Omit DSH_HOME to use DSH's default profile location, or set it to an operator-owned directory before all four DSH commands to isolate the installation.

The future connection flow will live in DSH Web Settings. Editing .env is not the intended onboarding path; see operations and configuration for the planned credential ownership model.

Local development

Install the checkout and run all local gates:

git clone https://github.com/canhta/dsh-autopilot.git
cd dsh-autopilot
pnpm install
pnpm run hooks:install
pnpm run check
mkdir -p .artifacts
pnpm pack --pack-destination .artifacts
pnpm run verify:package

pnpm run check runs Biome, strict type checking, the test suite and a clean production build. pnpm pack repeats the static gates and builds the distributable tarball. pnpm run verify:package installs that artifact into a disposable DSH profile, boots its built Host entry, and proves that package resolution rejects a missing Host entry with the expected diagnostic. Start with the contributor guide, then use the documentation map to find the relevant specification and source research.

Contributing

Contributions are welcome: clarify a requirement, verify a DSH integration against source, improve onboarding, or implement an agreed issue. Find or open a GitHub issue before substantial work so scope and dependencies are clear.

See Contributing for the local workflow, engineering rules and what to include in a pull request. Keep implementation progress and review evidence on GitHub, not in the specifications.

License

MIT. Community project; not an official DeepSeek product.