@lengmoxxl/dsh-git
A read-only git browser for the DeepSeek Harness Web GUI: a right-sidebar page with the session's working-tree changes and commit history, and the diff a click opens beside them. The host half reads the repository through ctx.fs and ctx.subprocess, so a routed (remote) execution world works unchange
The plugin will be installed here. Keep web if you are unsure.
npx -y @deepseek-ai/dsh plugin --profile web add @lengmoxxl/dsh-git@0.2.1
A read-only git browser for the DeepSeek Harness Web GUI: a right-sidebar page with the session's working-tree changes and commit history, and the diff a click opens beside them. The host half reads the repository through ctx.fs and ctx.subprocess, so a routed (remote) execution world works unchanged.
Git is published as @lengmoxxl/dsh-git and currently resolves to version 0.2.1. The Hub verifies its manifest and preserves the exact installation source for reproducible installs.
A DSH plugin that adds a Git page to the right sidebar: the working tree's changes and the recent commits on one side, and the diff a click opens on the other — read-only, highlighted, side by side. The list stays where it is, so two diffs can be put beside each other.
English | 中文
| Two columns, wrapped | Two columns, unwrapped | One column |
|---|---|---|
| The default: long lines wrap inside their half | Each half scrolls its own long lines; line numbers stay put | One column, each change as its removal then its insertion |
Needs Node 22.19+ (or 24+) and the DSH CLI.
From npm:
dsh plugin --profile web add @lengmoxxl/dsh-git
dsh --profile web
Or from the built tarball on the newest GitHub release — installing one compiles nothing and has no build for pnpm to allow:
dsh plugin --profile web add https://github.com/lengmoXXL/dsh-git/releases/latest/download/dsh-git.tgz
dsh --profile web
Releasing is manual; no workflow does it. From a clean main:
npm version patch --no-git-tag-version # or minor / major
git commit -am "Cut $(node -p "require('./package.json').version")"
npm run release # typecheck, tests, then npm publish
npm run release publishes @lengmoxxl/dsh-git to the public npm registry. The package's
publishConfig names that registry, so a mirror-configured machine still publishes to npm, and
the checks run first — a red check publishes nothing.
Then tag the release and attach its tarball:
version="$(node -p "require('./package.json').version")"
git tag -a "v${version}" -m "<the release note>"
git push --follow-tags
npm pack
cp "lengmoxxl-dsh-git-${version}.tgz" dsh-git.tgz
gh release create "v${version}" "lengmoxxl-dsh-git-${version}.tgz" dsh-git.tgz \
--title "<subject>" --notes "<the release note>"
dsh-git.tgz is the stable asset address the tarball install above uses.
MIT