DeepSeek Harness Plugin Hub

发布与管理完整 Harness Profiles,发现适合你的插件。

探索

插件目录环境预设文档中心动态

社区

发布插件联系我们报告问题

相关链接

Plugin Hub GitHubDeepSeek Harness 官方项目系统状态隐私说明
© 2026 DeepSeek Harness Plugin HubPowered byPaxTech

独立、非官方社区项目,与 DeepSeek 官方无隶属、授权或背书关系。

Arrowkey Nav — DeepSeek Harness 插件(DSH Plugin)
DeepSeek Harness Plugin Hub
ProfilesPlugins分类动态文档登录管理 Profiles
ProfilesPlugins分类动态文档登录
← Plugins

dsh-arrowkey-nav

Arrowkey Nav

DSH Web GUI 的方向键导航:上/下键切换当前工作区内的会话,左/右键切换工作区。

插件会安装到这里;不确定时保持 web。

npx -y @deepseek-ai/dsh plugin --profile web add dsh-arrowkey-nav@0.5.2
README兼容性版本

兼容性与来源证明

Arrowkey Nav 以 dsh-arrowkey-nav 发布,当前版本为 0.5.2。Plugin Hub 会校验它的 manifest,并保存精确安装来源,便于复现安装结果。

DSH 兼容范围
*
运行环境
web
发布来源
npm
Registry 更新时间
2026/10/16

版本

0.5.2stable
2026/10/4
0.3.4stable
2026/9/30
0.4.1stable
2026/9/30
查看其余 9 个版本收起版本
0.4.0stable
2026/9/30
0.3.3stable
2026/9/29
0.2.2stable
2026/9/25
0.3.2stable
2026/9/25
0.3.1stable
2026/9/20
0.2.1stable
2026/9/20
0.3.0stable
2026/9/18
0.2.0stable
2026/9/18
0.1.1stable
2026/9/15

相关插件

正在加载相关插件…

最新版
0.5.2
DSH
*
HMR
重启进程
Tree shaking
未声明可安全裁剪
解包体积
211 kB
文件数
29
Surface
web
许可证
MIT
发布源
npm
GitHub
★ 1
周下载
1,128
安全扫描
✓ v0.5.2 扫描通过
最近提交
2026/10/14
查看源码 ↗项目主页 ↗
README Badge

点击下方 Badge 复制 Markdown,粘贴到 README 即可。

这是你的 Plugin?认领权益 · 优先安全扫描

验证 package.json 声明的 GitHub 仓库,即可管理这个公开页面。认领后,Hub 会优先安排当前版本的安全扫描,并在通过后公开展示结果。

认领这个 Plugin →
报告问题

相关插件

继续浏览 ui-customization 分类下经过校验的插件。

Web App@deepseek-ai/dsh-web-appdsh 浏览器界面捆绑包:位于 dsh-base 之上的 Web 补丁层,加上运行时粘合插件(提供前端 dist、Web 界面提示符、bash 运行时变量和 URL 行)Experimental Agent Team Web Profile@deepseek-ai/dsh-experimental-agent-team-web-profile用于 Agent Teams Remote 和 UI 插件的实验性 Web 配置层Ab Chartdsh-ab-chart带有绘制其调用的浏览器卡片的图表渲染工具,封装在一个可发布的插件包中Whale Widgetdsh-whale-widgetDSH Web 界面右下角的 DeepSeek 余额小鲸鱼挂件:余额/今日已用/峰谷定价、自定义泡泡点击序列(文本/余额/今日/峰谷/图片/随机语句与并列加权选择)、逐行样式与字体、悬浮快捷编辑、音效与每轮消耗、自定义角色/动图/音效、吸附与翻转自定义

README

dsh-arrowkey-nav

English | 简体中文 | 日本語 | 한국어 | Français | Deutsch | Italiano | Русский | Español

Arrow-key navigation for the DSH Web GUI. Switch sessions without leaving the keyboard:

KeyActionScope
↑previous sessioninside the current workspace
↓next sessioninside the current workspace
←previous workspaceall workspaces
→next workspaceall workspaces

↑/↓ wrap around at the ends of the workspace and never cross into a neighbouring one; crossing is what ←/→ are for. After a switch the target row is scrolled into view, and focus returns to the composer if that is where the press started, so typing can continue immediately.

Version and DSH lines

One version serves every supported host line. Version 0.5.0 is tested with all rc releases of the DSH 0.1.0–0.2.0 lines — the exact whitelist is engines.dsh, distributed from the single source scripts/hosts.mjs by scripts/sync-hosts.mjs (hand edits fail npm run hosts:check):

DSH linetested rc releases
0.1.0rc.2, rc.3, rc.6, rc.7, rc.8
0.1.1rc.1, rc.2
0.1.2rc.1
0.1.5rc.1, rc.2, rc.3
0.1.7rc.1, rc.2
0.2.0rc.1, rc.2
  • There is no per-line build: both switching generations are dispatched by capability probing in one bundle (uiWorkspace.openSession on the 0.1.6+ generations, sessions.open on the older ones), so every host line runs the same code.
  • On the 0.1.0/0.1.1 lines (dsh-client-runtime generation) support is declaration-complete and unit-tested, but real-host keystroke verification is still pending; until then treat those cells as best effort.

Install

dsh plugin --profile web add dsh-arrowkey-nav -w

The registry's latest is the one version for every line. Each line also has a dist-tag pointing at the same build — dsh-arrowkey-nav@dsh-0.2.0, dsh-arrowkey-nav@dsh-0.1.5, and so on — if you prefer naming the line; the install target is identical. A host release outside the table above is rejected by the engines.dsh whitelist instead of mounting half-broken.

Restart the profile afterwards — a running instance does not hot-load a new bundle layer. Then reload http://127.0.0.1:3080.

Confirm the row is in the composed tree:

dsh web --dump-config | Select-String dsh-arrowkey-nav

A local checkout can be registered instead with dsh plugin --profile web add <absolute path to the checkout> -w; see INSTALL.md for the full guide, including upgrades, verification and removal.

Remove

dsh plugin --profile web remove dsh-arrowkey-nav

Restart, and the keys behave exactly as before the install: the listener is owned by the plugin's Cordis effect and is removed with it.

How it works

Identity comes from the two client controllers, never from the DOM: rows carry no data-* and no id, so a row cannot be asked what session it is.

  • Every switch goes through the capability-probed executor: ctx.uiWorkspace.openSession(id) on the DSH 0.1.6+ generations, ctx.sessions.open(id) on the older lines — one bundle, no per-line build. The details panel needs no handling: the shipped frame already closes it when the current session changes.
  • ctx.workspaces.list.getSnapshot() supplies the workspace order — the order ←/→ walks, and the source of each workspace's member list.

Which session is "next" follows the order the sidebar is drawing, not the controller's member order. Those disagree in exactly the case you notice: the sidebar reconciles its own persisted order with the membership and promotes recently-active sessions to the top, so an old session jumps to the first row the moment you open it. The plugin therefore reads the rendered row order out of the sidebar, and falls back to the controller order when the sidebar is not mounted (collapsed rail). A section is accepted only when its rows account for every session the controller reports for that workspace; an ambiguous or mismatched section falls back instead of guessing.

Keys are left alone when the event already belongs to somebody else: any modifier, IME composition, an event already handled upstream, or a focus inside a dialog, menu or another editable field (the sidebar's session search, a rename box). The listener registers in the capture phase but only calls preventDefault() when it actually navigates.

The composer is the one conditional case. An empty composer yields its arrow keys — there is no caret to move, so the key is free — which is what lets you navigate right after sending a message, while the composer still holds focus. Once the composer holds a draft, its arrow keys belong to the caret again, so editing a prompt is never hijacked.

The browser half has no React components, no CSS and no platform-module requests, and the package has no runtime dependencies — lib/client.js is generated by scripts/build-client.mjs into the module-loader contract the page expects.

Development

npm run typecheck   # both compiler faces
npm test            # resolver unit tests + built-bundle smoke tests
npm run build       # regenerate lib/client.js after editing src/client

npm run build needs typescript; if it is not installed in this package, point DSH_TYPESCRIPT at an existing typescript module directory.

Known limitations

  • A collapsed workspace group does not scroll. Its rows are not mounted, and dsh exposes no public way to expand a group, so the switch happens but the target row stays out of sight. The workspace holding the current session is kept expanded by dsh itself, so ↑/↓ are unaffected.
  • A rail-collapsed sidebar does not scroll for the same reason: the tree is not mounted. The switch still happens.
  • "In one list" mode has no workspace sections, but ←/→ still walk the controller's workspace order, so the list may appear to jump between sections.
  • Scrolling is best effort. Any lookup failure is swallowed: the selection has already moved, and a missing row must never turn into a wrong one.
  • Snapshot fields are pre-stable. sessions and workspaces snapshot shapes are pre-stable — the tested host releases are exactly the engines.dsh whitelist (engines.dsh: 0.1.0-rc.2 || 0.1.0-rc.3 || 0.1.0-rc.6 || 0.1.0-rc.7 || 0.1.0-rc.8 || 0.1.1-rc.1 || 0.1.1-rc.2 || 0.1.2-rc.1 || 0.1.5-rc.1 || 0.1.5-rc.2 || 0.1.5-rc.3 || 0.1.7-rc.1 || 0.1.7-rc.2 || 0.2.0-rc.1 || 0.2.0-rc.2). If a dsh upgrade changes them, src/client/navigate.ts and src/client/apply.ts are the only files to revisit; a host that exposes neither switching API leaves the plugin inert rather than failing the page.

Layout

src/index.ts                node half: loader entry, installs nothing
src/client/constants.ts     keys owned, DOM anchors read
src/client/navigate.ts      narrow waist: snapshot types + arrow resolver
src/client/apply.ts         execution: open / blank-first / connectWorkspace
src/client/dom.ts           read-only DOM: scroller, section binding, scroll, focus
src/client/session-nav.ts   key guards + one arrow press end to end
src/client/index.ts         Cordis entry: inject + one capturing listener
scripts/build-client.mjs    generates lib/client.js
tests/                      resolver unit tests + bundle smoke tests

License

MIT