OpenViking in the DSH web GUI: a Studio panel, a per-session memory-commit status pill with its commit timeline, and a right-sidebar tab showing what the current session retrieves.
Install
# from npm (prebuilt)
dsh plugin --profile web add dsh-openviking-enhance
# from a prebuilt release tarball
dsh plugin --profile web add "https://github.com/A2chitect/dsh-openviking-enhance/releases/latest/download/dsh-openviking-enhance.tgz"
# from GitHub (first run asks for allowBuilds approval — follow the hint, retry)
dsh plugin --profile web add github:A2chitect/dsh-openviking-enhance
Any plugin you install runs third-party code with your own permissions — it can read your files, use your credentials, and reach the network, and tool approvals don’t sandbox it. GitHub-sourced plugins also run build scripts at install time — pnpm blocks those until you allow them, so an install can stop with ERR_PNPM_GIT_DEP_PREPARE_NOT_ALLOWED or ERR_PNPM_IGNORED_BUILDS; dsh prints the exact key to add under allowBuilds in your profile’s pnpm-workspace.yaml, and the install works on the next run. Allowing a build is a trust decision: only install sources you trust, and pin a commit (github:owner/repo#sha).
README
English | 中文
v0.2.3 · Changelog
Brings your local OpenViking memory server into the DeepSeek Harness (DSH) Web GUI: a Studio panel in the left sidebar, and a commit status pill under the message box that shows what each session commit did to your memories.
Nothing needs to be patched in DSH or in the OpenViking plugin — it mounts as an ordinary DSH bundle.
What you get
OpenViking Studio, inside DSH. A new row at the bottom of the left sidebar opens the OpenViking server's own Studio UI in the main area, so you can browse memories, sessions and retrieval without leaving the app or switching to a browser.
Per-session commit status. OpenViking writes memory in commits: a session's turns accumulate until a token threshold is reached (or the session ends), then they are archived and the memories are extracted. The pill under the message box tells you where the session you are looking at stands.
The pill follows the app's language (see Notes); in English it reads:
| Pill | Meaning |
|---|---|
OV · not committed |
Nothing from this session has been committed yet |
OV · 12.3k/20k |
Turns are accumulating towards the commit threshold |
OV · extracting… |
A commit is being archived and its memories extracted |
OV · 3 commits |
Three commits so far |
OV · extraction failed |
The newest commit was archived but its memories could not be extracted |
OV · cancelled |
The newest commit was cancelled before its memories were extracted |
OV · unavailable |
The local OpenViking server cannot be reached |
Click the pill for details:
- a timeline of the most recent 3 commits — when each happened, whether its extraction finished or failed, and how many memories it added, updated or deleted (the rest are one click away);
- clicking a commit lists the exact memories it changed, with their
viking://paths; - any failed extraction, with the time and the reason the server reported. Failures older than the newest commit stay listed there without changing the pill.
The panel and the pill read only. This plugin never commits, writes or deletes anything in OpenViking.
What this session retrieves. The right sidebar gains a Memory recall tab: it shows what OpenViking pulls in for the session you are looking at
— the query it searched with (that session's most recent message, or one you type
yourself), every hit in each of its three sources (memories, resources, skills)
with its score — graded from red through orange to green — its file name, its kind
(entity, event, …) and its abstract. The full viking:// path is on hover, and
opening a row loads that entry's whole text. The plan the server retrieved with is there
too. Open it from the right sidebar's +
guide; it is per session, like the column itself.

The Studio panel, the sidebar row that opens it, and the commit pill below the composer.
Requirements
| DSH | 0.2.0-rc.2 or newer (desktop or web profile; verified on 0.2.1-rc.3) |
| OpenViking | A local server; 0.5.1.1 tested. Studio is served at /studio/ on the same port |
| Memory plugin | @openviking/dsh-memory-plugin recommended — it is what commits sessions. Without it the panel still works, but pending-token thresholds are unknown |
Install
Install it from the Plugins page (Add plugin → package name or tarball), or:
# from npm
dsh plugin --profile desktop add dsh-openviking-enhance
# or the prebuilt tarball from the latest release
dsh plugin --profile desktop add https://github.com/A2chitect/dsh-openviking-enhance/releases/latest/download/dsh-openviking-enhance.tgz
Installing straight from a Git URL is refused by pnpm — the package asks to run a build script and pnpm blocks those until they are allowed — so a source checkout is installed as a tarball instead. The client half is a prebuilt bundle: a source install would have nothing to load.
pnpm pack && dsh plugin --profile desktop add ./dsh-openviking-enhance-<version>.tgz
Then restart the DSH app once: the host half is loaded at startup. To remove it:
dsh plugin --profile desktop remove dsh-openviking-enhance
Configuration
Everything has a sensible default — a standard local setup needs no configuration at all. To change something, open Plugins in the sidebar, pick this plugin, and use Configure on its row: the form carries the fields below, a check button that probes the address before you save, and a default button per field that clears the override instead of writing an empty value.
The same settings can still be written by hand in your profile's patch file
(~/.dsh/profiles/desktop/cordis.patch.yml), under the row openviking-enhance:
- id: openviking-enhance
name: 'dsh-openviking-enhance'
config:
endpoint: http://127.0.0.1:1933
| Field | Default | Meaning |
|---|---|---|
endpoint |
from ~/.openviking/ovcli.conf, else http://127.0.0.1:1933 |
OpenViking base URL |
apiKey |
from ovcli.conf |
Only needed if the server requires authentication |
account / user |
default / default |
Identity the panel reads under |
studioPath |
/studio/ |
Where Studio is served on that origin |
cacheTtlMs |
2500 |
How long a status answer is reused |
recallCacheTtlMs |
15000 |
How long one retrieval answer is reused |
showSidebarEntry |
true |
Interface switch: the OpenViking entry in the left sidebar |
showCommitStatus |
true |
Interface switch: the commit status pill under the message box |
showRecallPanel |
true |
Interface switch: the Memory recall tab in the right sidebar |
The three interface switches control the three surfaces independently. They take effect as soon as you save — the GUI mounts or unmounts the surface without a reload or a restart. The Configure form itself is never hidden, so a surface switched off can always be switched back on there. Hiding the sidebar entry also unmounts the Studio page (it loads fresh when shown again), and hiding the recall tab closes an open recall page as soon as the conversation is back on screen — a page that is open in a background pane has to be closed by hand, because the harness exposes no way to enumerate tabs.
Troubleshooting
No OpenViking row in the sidebar, or no pill under the message box. First check the plugin's own switches (Plugins → this plugin → Configure → Interface): a surface may be switched off, and the switches are independent. Otherwise the client half is served as a file and picked up on page load. Reload the window (⌘R). If it is still missing, restart the app.
I hid the OpenViking row / pill / recall tab and want it back. Open Plugins → dsh-openviking-enhance → Configure on its row and switch it back on, then save. That form is always available, even with all three surfaces hidden.
The panel says it cannot reach OpenViking.
Start the server and check it directly: curl http://127.0.0.1:1933/health. The
panel shows the address it tried, which helps when endpoint is not the default.
The pill says extraction failed.
The commit was archived but OpenViking could not turn it into memories — those
memories are not in your library. Click the pill for the server's own error; it is
usually a problem with the extraction model configured in ~/.openviking/ov.conf.
The pill shows a token count instead of a commit count.
@openviking/dsh-memory-plugin is not installed, so the commit threshold is
unknown. Commits themselves still work; only the progress denominator is missing.
The timeline shows only 3 commits. That is the default. Click show all.
There is no recall tab in the right sidebar.
The tab is reached through that column's own + guide, and it only exists after a
window reload (the client half is a file the page loads). If DSH is older than
0.2.0-rc.2 it has no right sidebar to contribute to: the row is skipped and the
Studio panel and the pill keep working.
I changed the code and nothing happened. The two halves reload differently: the client half after a window reload, the host half only after an app restart.
Notes
- The plugin's own text follows the app's language. It ships Chinese and English and reads the locale DSH sets, so switching the app's language switches this plugin's copy too; anything else falls back to English.
- OpenViking cleans up its commit task records over time, so the failure list covers recent commits only. The archives themselves are permanent.
- The plugin's internal routes answer loopback requests only, and only from the DSH window's own origin.
Development
pnpm install
pnpm run build # lib/index.js (host) + lib/client.js (browser)
pnpm test # typecheck, packaging contract, unit tests, smoke harnesses
pnpm run watch # rebuild on change
The smoke harness prints the commit timeline without needing the GUI, and skips the
live-data part when OpenViking is not running (SMOKE_REQUIRE_SERVER=1 makes that a
failure instead). The code comments explain how the pieces fit together.
The version lives in package.json and is tagged vX.Y.Z in git; while it is 0.x
the internals may still change. See CHANGELOG.md for what each
release contains, and RELEASING.md for the release steps and the
GUI acceptance checklist — that one is a maintainer document, Chinese only.
Links
More in this category
zhu1090093659/dsh-web#packages/dsh-task-board★ 10172
Task board for the dsh web GUI: a sidebar multi-column kanban whose cards run in real DSH agent sessions and can also be scheduled with cron expressions, executed host-side even with the browser closed.
zhu1090093659/dsh-web#packages/dsh-web-all★ 10172
Plugin and skin collection for the DSH Web UI: task board, Git graph, right-side panel, remote mobile UI, pet, live token stats, and a skin center.
ccch1mneyyy/dsh-TUI★ 7101
Claude Code-style full-screen terminal UI: pixel-whale header, live status line, and streaming thought expansion.
MeteorNOX/DeepSeek-Balance-Whale-Widget★ 6959
A fixed-corner whale widget for the DSH web GUI — balance, today's usage and per-turn cost with peak/off-peak pricing, editable balance-alert and daily-budget bubbles, a module-based custom bubble queue with A/B weighted choices and random lines or images, 30+ vendor templates (OpenAI, OpenRouter, Kimi, SiliconFlow, Ark, Zhipu, MiniMax and more) with per-model balance and subscription quota, plus task-end sound, imported audio, custom roles and a resource manager. Local-only, no telemetry.
omdsh-dev/DSH-better-sidebar★ 4959
Full sidebar workbench with file rendering and editing, terminal, Git, and subagents; third-party plugins can register new tabs.
Devin-AXIS/deepseek-design#deepseek-idesign★ 1744
Visual design studio for websites, app prototypes, posters, cards, reports, and magazines, with templates, direct element editing, selection-aware AI draft handoff, and export.
Community comments
Comments are public GitHub Discussions. Loading them connects to GitHub and Giscus; a GitHub account is required to post.