You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[dsh-plugin.org | dsh-plugin-hub] plugin distribution incomplete: loopx-project/loopx #6544
[ERROR] Command failed with exit code 1: git ls-remote "https://github.com/loopx-project/loopx.git" HEAD "HEAD^{}"
This error happened while installing a direct dependency of C:\Users\陈益宁\.dsh\profiles\desktop
pnpm: Command failed with exit code 1: git ls-remote "https://github.com/loopx-project/loopx.git" HEAD "HEAD^{}"
at getFinalError (file:///C:/Users/%E9%99%88%E7%9B%8A%E5%AE%81/AppData/Local/Programs/DeepSeek%20Harness/resources/runtime/pnpm/dist/pnpm.mjs:34109:14)
at makeError (file:///C:/Users/%E9%99%88%E7%9B%8A%E5%AE%81/AppData/Local/Programs/DeepSeek%20Harness/resources/runtime/pnpm/dist/pnpm.mjs:36416:21)
dsh: plugin command failed; diagnostics: C:\Users\陈益宁\.dsh\profiles\desktop\.plugin-manager\logs\operation-gI6GsF\pnpm.log
dsh: git-hosted plugins build on install via their prepare script, which pnpm blocks until allowed — add the exact key pnpm printed above under allowBuilds in C:\Users\陈益宁\.dsh\profiles\desktop\pnpm-workspace.yaml, then re-run
This error was produced by the dsh-plugin-hub installer bundled with DeepSeek Harness.
The error shown is git ls-remote failing while resolving the repository. The excerpt does not establish a blocked prepare script, so it is insufficient evidence for changing allowBuilds.
There is also an installation-target problem: git+https://github.com/loopx-project/loopx.git selects the monorepo root (loopx-repository), while the built DSH plugin is a separate package. The installation/recovery guide documents that distinction.
For the reported DSH 0.2.0-rc.2, use the published plugin beta.6 package, keeping your desktop profile:
This bypasses the catalog's Git target. It still requires access to the release asset and any required package dependencies. The profile should contain loopx-goalbar, loopx-init-command, loopx-driver and loopx-shadow-observer; restart DSH and inspect the initialization result. Loading prepares a private LoopX runtime/skills when needed. Installation alone does not activate the Agent continuation loop; that requires invoking the loopx skill in the exact Session and a valid binding.
I downloaded the published tarball today and verified its SHA-256 against GitHub's asset digest:
The archive contains the compiled entry and patch, and its manifest includes the reported DSH/Node versions. This is package inspection; I have not reproduced installation on your Windows desktop.
If the pinned URL still fails, the useful next evidence is the actual command and final inner Git/pnpm error block, with credentials and identifying paths removed. For beta.6, close DSH before CLI removal; its published release documents a hot-uninstall limitation.
中文:先区分 Git 拉取失败与脚本权限,再把安装目标从仓库根目录换成上面的固定发行包,安装与检查都保留 desktop。这还不能证明原 Windows 环境已恢复,所以本 issue 继续保持开放。
Published dsh-loopx-plugin 0.1.1-beta.7 alongside LoopX v2.4.0 (release commit a6ffb3be6e7bdb48e02311ec58d618200fe0501c, requiring loopx>=2.4.0 and qualifying DSH 0.2.2-rc.1..rc.3 while keeping 0.1.5..0.2.1-rc.2). 0.1.1-beta.7 includes the shared Web server hot-uninstall fix (#6102), the Personal Workspace LoopX sidebar panel (#8352), Windows native continuation & GoalBar path matching (#8504), and GoalBar admission diagnostics (#8879).
Pinned GitHub Release Tarball Verification
For DSH 0.2.2-rc.1..rc.3 (keep --profile desktop if you are on desktop, or --profile web for web):
Downloaded remote release asset dsh-loopx-plugin-0.1.1-beta.7.tgz (88,832 bytes) and confirmed exact SHA-256 match against the clean build from a6ffb3be6e7bdb48e02311ec58d618200fe0501c:
Verified remote GitHub tarball installation in an isolated macOS DSH 0.2.2-rc.3web profile (dsh plugin --profile web add ... -> [email protected], --dump-config loaded loopx-goalbar, loopx-init-command, loopx-driver, loopx-shadow-observer), plus isolated bootstrap of PyPI loopx==2.4.0. Windows desktop full-journey acceptance remains unverified here.
Catalog & npm Distribution Status
Directory PR (OPEN):awesome-dsh-plugin/awesome-dsh-plugin#17660 updates data/plugins/loopx-project__loopx--packages-dsh-loopx-plugin.yml to pin the immutable 0.1.1-beta.7 GitHub release tarball URL (generate-readme.mjs --check, check-submission.mjs, and git diff --check passed).
npm registry status:dsh-loopx-plugin is not yet published on registry.npmjs.org (E404). PR #9224 fixed .github/workflows/dsh-plugin-publish.yml's ./output/ relative tarball argument, and re-dispatched run 44957442899 inspected the 34-file tarball (shasum: 89c6cf1b04352a7ed7c0931978d77e1031e9023e) cleanly before stopping at ENEEDAUTH (npm package creation / Trusted Publisher binding on npmjs remains an owner setup gate).
Because Windows full-journey reproduction, upstream catalog propagation, and npm Trusted Publisher setup remain pending, this issue stays open.
Activity
loopx-agent commentedon Oct 23, 2026
The error shown is
git ls-remotefailing while resolving the repository. The excerpt does not establish a blockedpreparescript, so it is insufficient evidence for changingallowBuilds.There is also an installation-target problem:
git+https://github.com/loopx-project/loopx.gitselects the monorepo root (loopx-repository), while the built DSH plugin is a separate package. The installation/recovery guide documents that distinction.For the reported DSH 0.2.0-rc.2, use the published plugin beta.6 package, keeping your desktop profile:
This bypasses the catalog's Git target. It still requires access to the release asset and any required package dependencies. The profile should contain
loopx-goalbar,loopx-init-command,loopx-driverandloopx-shadow-observer; restart DSH and inspect the initialization result. Loading prepares a private LoopX runtime/skills when needed. Installation alone does not activate the Agent continuation loop; that requires invoking theloopxskill in the exact Session and a valid binding.I downloaded the published tarball today and verified its SHA-256 against GitHub's asset digest:
The archive contains the compiled entry and patch, and its manifest includes the reported DSH/Node versions. This is package inspection; I have not reproduced installation on your Windows desktop.
If the pinned URL still fails, the useful next evidence is the actual command and final inner Git/pnpm error block, with credentials and identifying paths removed. For beta.6, close DSH before CLI removal; its published release documents a hot-uninstall limitation.
中文:先区分 Git 拉取失败与脚本权限,再把安装目标从仓库根目录换成上面的固定发行包,安装与检查都保留
desktop。这还不能证明原 Windows 环境已恢复,所以本 issue 继续保持开放。loopx-agent commentedon Nov 21, 2026
Published
dsh-loopx-plugin 0.1.1-beta.7alongside LoopXv2.4.0(release commita6ffb3be6e7bdb48e02311ec58d618200fe0501c, requiringloopx>=2.4.0and qualifying DSH0.2.2-rc.1..rc.3while keeping0.1.5..0.2.1-rc.2).0.1.1-beta.7includes the shared Web server hot-uninstall fix (#6102), the Personal Workspace LoopX sidebar panel (#8352), Windows native continuation & GoalBar path matching (#8504), and GoalBar admission diagnostics (#8879).Pinned GitHub Release Tarball Verification
For DSH
0.2.2-rc.1..rc.3(keep--profile desktopif you are on desktop, or--profile webfor web):Verification recorded today:
dsh-loopx-plugin-0.1.1-beta.7.tgz(88,832bytes) and confirmed exact SHA-256 match against the clean build froma6ffb3be6e7bdb48e02311ec58d618200fe0501c:DSH 0.2.2-rc.3webprofile (dsh plugin --profile web add ...->[email protected],--dump-configloadedloopx-goalbar,loopx-init-command,loopx-driver,loopx-shadow-observer), plus isolated bootstrap of PyPIloopx==2.4.0. Windows desktop full-journey acceptance remains unverified here.Catalog & npm Distribution Status
data/plugins/loopx-project__loopx--packages-dsh-loopx-plugin.ymlto pin the immutable0.1.1-beta.7GitHub release tarball URL (generate-readme.mjs --check,check-submission.mjs, andgit diff --checkpassed).dsh-loopx-pluginis not yet published onregistry.npmjs.org(E404). PR #9224 fixed.github/workflows/dsh-plugin-publish.yml's./output/relative tarball argument, and re-dispatched run 44957442899 inspected the34-file tarball (shasum: 89c6cf1b04352a7ed7c0931978d77e1031e9023e) cleanly before stopping atENEEDAUTH(npm package creation / Trusted Publisher binding on npmjs remains an owner setup gate).Because Windows full-journey reproduction, upstream catalog propagation, and npm Trusted Publisher setup remain pending, this issue stays open.
中文:
dsh-loopx-plugin 0.1.1-beta.7已随 LoopXv2.4.0发布(修复热卸载断开共享 Web 服务#6102与 Windows 路径/续跑匹配#8504,要求loopx>=2.4.0)。已验证 GitHub Release 远端 tarball 的 SHA-256 与隔离 macOS DSH0.2.2-rc.3安装结果,并已开启目录更新 PR#17660;npmregistry.npmjs.org仍待仓库 owner 完成首次包发布 / Trusted Publisher 配置(run44957442899返回ENEEDAUTH),且 Windows 桌面全链路仍待验证,故保持本 issue 为开放状态。