This article is derived from the plugin's already-indexed fields (wiki / faq / compatibility_json / readme), not freshly generated by AI. Source field is noted at the end of each section.

Quick start

deepseek-harness-desktop

— source: plugin_wiki.wiki_content

Install & verify

dsh plugin --profile web add github:chokwinlee/deepseek-harness-desktop#path:test/fixtures/sample-plugin

Run the command above in your DSH Web Profile. Then enable the plugin in the plugin list.

— source: plugins.install

Key points

• Usage at a glance on macOS — see today and seven-day token totals, estimated cost, active task count, and aggregate running throughput without leaving the current session.
• Compact macOS package — stays under 90 MB while bundling the complete Harness runtime, using Tauri and the system WKWebView instead of shipping Chromium.
• Visible runtime alignment — the sidebar identifies both the Desktop release and its bundled Harness version, such as DSH Desktop v0.3.0 · Harness rc.8.
• Ready to run — includes everything needed to start Harness, with no separate Node.js installation or terminal command. The app starts and stops the local runtime automatically.
• Read CONTRIBUTING.md before opening a pull request.

— source: plugin_wiki.readme_en (fallback readme_raw)

FAQ

What does this plugin do?

It has no practical function for end users; it is merely a standard test sample used by the deepseek-harness-desktop project's scripts/verify-tauri.sh to verify the dsh plugin add/remove pipeline. It does not inject any patches itself.

What changes will happen to my DSH after installation?

There will be no visible changes. The cordis.patch.yml content is an empty array [] and will not inject any modifications to the host; only ~/.dsh/profiles/web/package.json's dependencies and dsh.profile.bundles list will have one additional entry.

verify-tauri.sh uses link: instead of github: for installation. Is there a difference?

There is a difference. link: uses local path resolution and is used for CI smoke testing, while github: pulls from remote repositories; both will ultimately write the fixture into the profile manifest, but only the link: form will be automatically run through by verify-tauri.sh.

Can this fixture run independently outside the repository?

No, it cannot. It relies on test/fixtures/fake-dsh.mjs from the same repository, combined with the FAKE_DSH_MODE=plugin-install-ready environment variable, to simulate the "plugin installation successful" path; using it separately without this script will lack the target being tested.

— source: plugin_wiki.faq_json

Compatibility

• DSH: 未声明
• Node: 未声明

— source: plugin_wiki.compatibility_json

Pitfalls

Review the upstream repo before installing. This guide is auto-derived from indexed fields and may lag the latest release. If anything contradicts the official docs, treat the upstream source as authoritative.

— source: general rule