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 继续保持开放。
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 继续保持开放。