@dipertq/dsh-openviking-status
DeepSeek Harness composer 的极简 OpenViking 状态标签和弹出窗口
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add @dipertq/dsh-openviking-status@0.3.2Openviking Status 以 @dipertq/dsh-openviking-status 发布，当前版本为 0.3.2。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
Minimalist OpenViking status chip and popover for DeepSeek Harness (DSH Desktop / Web).
This DSH UI plugin adds a chip to the composer stats row
(conversation.composer.dock), alongside 24 turns 645 steps. It provides
at-a-glance transparency into OpenViking memory management:
viking:// files injected into the current conversation.~/.openviking/ovcli.conf, ~/.openviking/ov.conf, or the OPENVIKING_API_KEY environment variable./openviking-status/api/*), ensuring the chip and popover work reliably when accessing DSH remotely without CORS or localhost conflicts.See CONTEXT.md, ADR 0001, and ADR 0002.
dsh plugin add @dipertq/dsh-openviking-status
Then restart DSH Desktop. That is the whole procedure: DSH reads the package's
dsh.bundle.patch, adds it to dsh.profile.bundles itself, and the chip appears
in the composer bar.
Equivalent, and useful when the registry is unreachable. Use a version-pinned URL:
dsh plugin add https://github.com/dipertq/dsh-openviking-status/releases/download/v0.3.2/dipertq-dsh-openviking-status-0.3.2.tgz
Not /releases/latest/download/…: that URL keeps its name while its content
changes, so pnpm records no integrity for it and every later pnpm install in
the profile fails with ERR_PNPM_MISSING_TARBALL_INTEGRITY.
github:dipertq/...?That form works, but costs an extra manual step. A github: spec makes pnpm
build the package on your machine, and pnpm blocks build scripts until the
package is allowlisted. The pnpm shipped with DSH Desktop (11.8.0) only matches
a commit-pinned key, which changes on every push — so the entry has to be
re-added for each new version:
# ~/.dsh/profiles/desktop/pnpm-workspace.yaml
allowBuilds:
"@dipertq/dsh-openviking-status@https://codeload.github.com/dipertq/dsh-openviking-status/tar.gz/<commit-sha>": true
Both recommended forms ship lib/ already compiled, so no build script runs and
no allowlist entry is needed. See ADR 0004.
ERR_PNPM_IGNORED_BUILDSIf a previous github: attempt left entries in your profile's
pnpm-workspace.yaml, pnpm may have written them with a literal placeholder:
allowBuilds:
"@dipertq/dsh-openviking-status@https://...": set this to true or false
A placeholder means "not decided yet", so every install fails until it is a real boolean. Delete those stale entries — neither recommended install path needs any of them:
allowBuilds:
node-pty: true
main (tsc, README install-URL
check, pnpm test, pnpm run build).v* tag builds the package, verifies it, and publishes a
GitHub Release with the versioned .tgz.pnpm run release:patch # 0.1.0 -> 0.1.1
pnpm run release:minor # 0.1.0 -> 0.2.0
pnpm run release:major # 0.1.0 -> 1.0.0
Releases publish to npm through
trusted publishing: GitHub Actions
authenticates over OIDC with short-lived credentials, so there is no NPM_TOKEN
secret to store or rotate, and each release carries a provenance attestation
proving which commit and workflow built it.
This is already configured, so a release needs nothing beyond the usual
pnpm run release:*. The one-time setup was: publish the first version by hand
(trusted publishing is configured per package, so the package has to exist),
then register a GitHub Actions publisher on the package's
Settings → Trusted Publisher page — user dipertq, repository
dsh-openviking-status, workflow release.yml, environment blank.
MIT