[dsh-plugin.org | dsh-plugin-hub] plugin install failed: loopx-project/loopx #5671

Activity

1. Dante-dan commented on Oct 5, 2026

   

   Dante-dan

   on Oct 5, 2026

   More actions

   I checked the released beta.5 package artifact. Its @deepseek-ai/dsh peer range ends before 0.2.0-0, so it does not declare compatibility with the 0.2.0-rc.2 version in this report. PR #5589 is open and is preparing 0.2.0-rc.2 qualification for beta.6; that is not a released fix yet. The beta.5 cordis.patch.yml also does not reference @deepseek-ai/dsh-desktop-host.

   Could you share the relevant lines from ~/.dsh/profiles/desktop/hub.log around this failure? That should show whether the missing dsh-desktop-host/lib/cli.js is part of the unsupported-version path or a separate host/package-resolution problem. Please omit any credential values if they appear in that excerpt.
2. loopx-agent commented on Oct 5, 2026

   

   loopx-agent

   on Oct 5, 2026

   Collaborator

   More actions

   This report's immediate error is a missing @deepseek-ai/dsh-desktop-host/lib/cli.js in the packaged Windows desktop host, before LoopX is loaded. It must not be classified as a missing LoopX entry file or claimed fixed merely by publishing beta.6. Released Hub 1.4.13 and 1.4.14 both already choose the application's desktop bootstrap; the desktop bootstrap/module packaging path still needs Windows/upstream readback. Preserve the desktop application's own profile authority rather than bypassing it with another CLI.

   After the host path is repaired, use beta.6: DSH 0.2 correctly rejects the current beta.5 catalog package. The published package and catalog/Hub adoption links are below; the full Windows desktop journey remains unverified.

   Published beta.6 and illustrated upgrade/recovery guide are available. The immutable GitHub tgz includes the compiled Host, Client, Driver and initializer; downloaded bytes match the tagged build. Native DSH 0.2 URL installation, compatible beta.5-to-beta.6 CLI upgrade/removal, offline plugin-tgz install/removal and real macOS browser Start/Pause with released CLI 1.2.4 were qualified.

   The live catalog still selects beta.5. Catalog #6633 and Hub #98 need upstream adoption/release before claiming full market recovery. Released Hub 1.4.14 supports GitHub packages without publishing LoopX on npm. Windows desktop full-journey acceptance remains open under #5208.

   Native browser hot uninstall failed (Web disconnected, package dependency retained); the tested recovery is to close DSH, use native CLI removal, then restart. This differs from the passing CLI/backend removal paths. Keeping the report open while the relevant upstream/platform journey remains incomplete.