DeepSeek Harness Plugin Hub

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

探索

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

社区

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

相关链接

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

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

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

dsh-session-favorites

Session Favorites

DSH 会话收藏夹插件:收藏会话、按工作区分组、@ 引入、多设备一致

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

npx -y @deepseek-ai/dsh plugin --profile web add github:hiuga0321/dsh-session-favorites#192808e995e55345a67018a452a8887179208b7e
README兼容性版本
Favorites panel grouped by workspace, with a search box, starred rows, and the sidebar entry that opens it

兼容性与来源证明

Session Favorites 以 dsh-session-favorites 发布,当前版本为 0.1.1。Plugin Hub 会校验它的 manifest,并保存精确安装来源,便于复现安装结果。

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

版本

0.1.1stable
2026/10/9

相关插件

正在加载相关插件…

最新版
0.1.1
DSH
*
HMR
重启进程
Tree shaking
未声明可安全裁剪
解包体积
未提供
文件数
未提供
Surface
web
许可证
MIT
发布源
github
GitHub
★ 0
周下载
0
最近提交
2026/10/9
查看源码 ↗
README Badge

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

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

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

认领这个 Plugin →
报告问题

相关插件

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

Hindsight Coding Agents@vectorize-io/hindsight-coding-agents面向编程代理的仅反思式 Hindsight 长期记忆(可插拔支持多种运行框架:opencode、……),自动在后台导入(无需设置 CLI)。Memsearch Dsh@zilliz/memsearch-dsh适用于 DeepSeek Harness 的 MemSearch 插件:在多个代理之间共享 Markdown 记忆,支持捕获、步骤前上下文注入、记忆召回技能和技能候选审核面板。Memory@furongjun1999/dsh-memory灵枢(Lingshu·líng shū)DeepSeek Harness 插件:完整大脑——长期记忆/知识飞轮/自我认知/递归反思接入 DSH,对话自动沉淀进 md_cg 认知图(md 文档)Archive Manager@michengai/dsh-archive-manager归档、恢复、收藏和永久删除会话,并诊断损坏的会话日志。

README

DSH Session Favorites

Keep the conversations you return to, one click away

简体中文 · MIT

DSH Session Favorites is a community-maintained DeepSeek Harness (DSH) plugin, not an official DeepSeek AI product.

What you can do

Star the conversations you keep coming back to, then find them without scrolling the sidebar.

  • Save a conversation: star it from the session header, or add it from the favorites list.
  • Browse by workspace: favorites are grouped by the workspace they belong to, so long lists stay readable.
  • Find one fast: search titles from the top of the list.
  • Bring one into the prompt: type @ in the composer to insert a favorited session.
  • Keep names current: rename a favorite and the real conversation is renamed too, through DSH's own rename path.
  • See the same list everywhere: favorites are stored on the host, so every tab and browser sharing a profile agrees.
  • Reach archived favorites: an archived favorite still opens, without changing its archived state.
  • Clear out dead entries: deleted conversations are marked and can be cleaned up in one confirmed step.

Screenshots

Open Favorites at the bottom of the sidebar, above the settings button:

Favorites panel grouped by workspace, with a search box, starred rows, and the sidebar entry that opens it

Each favorite carries a star, and the sidebar entry shows how many favorites the current profile holds. Rows are grouped under the workspace they belong to and rename/remove actions appear on hover.

Prerequisites

  • A working DeepSeek Harness Web installation with dsh available in your terminal.
  • Supported DSH versions: 0.1.5-rc.2 through 0.2.1-alpha.1.
  • Node.js >=22.15.

Installation

Examples use the web profile. Replace it with the profile you actually use.

Ask an agent to install it

Send this prompt to an agent that can run terminal commands on your computer:

Install the latest dsh-session-favorites into my local DSH web profile using the official npm registry. Check the plugin configuration afterward, then explain how to reload DSH and open the favorites list.

Install manually

Run in PowerShell:

[Console]::OutputEncoding = [System.Text.Encoding]::UTF8
$OutputEncoding = [System.Text.Encoding]::UTF8

dsh plugin --profile web add dsh-session-favorites@latest --registry=https://registry.npmjs.org/

Restart DSH Web, then hard-refresh your browser with Ctrl+Shift+R. The Favorites entry appears at the bottom of the sidebar.

Usage

GoalAction
Favorite the current conversationClick the star in the session header
Open your favoritesSidebar footer → Favorites
Find a favoriteType in the search box at the top of the list
Open a favoriteClick its row
Insert a favorite into a promptIn the composer, type @ and pick a session
Rename a favoriteHover the row → rename; the real conversation is renamed too
Remove one favoriteHover the row → remove → confirm
Clean up deleted conversationsUse the banner shown next to the list, then confirm

The panel closes only through its close button, so clicking elsewhere will not dismiss it mid-task. Removing a favorite always asks for confirmation, and bulk cleanup uses the same dialog.

Favorites are stored in a favorites storage domain on the host. DSH's own session data is never modified, and nothing is written outside your DSH profile.

Archived conversations

An archived favorite stays clickable, and opening it does not change its archived state. The plugin deliberately does not call DSH's unarchive API, so after you open one it is still archived — you can just read it. To actually unarchive it, use DSH's native Unarchive; the two operations are independent. If the small compatibility patch this relies on cannot be applied, the plugin reports it rather than failing silently, and opening an archived favorite degrades to a visible message.

Renaming

Renaming a favorite renames the underlying conversation through DSH's own session.rename, the same path the native sidebar uses. If that rename succeeds but syncing the plugin's stored copy fails, the conversation keeps its new name and the plugin only logs a warning — your rename is never rolled back.

Updates

To move to a newer release, rerun the installation command with the version you want, then restart DSH Web and hard-refresh the browser:

dsh plugin --profile web add dsh-session-favorites@latest --registry=https://registry.npmjs.org/

FAQ

Why is the entry missing after installation?

Restart DSH Web and hard-refresh your browser, and make sure you installed into the profile you are actually using. If the entry is still missing, confirm the plugin resolved:

dsh --profile web --dump-config

The output should include session-favorites, and the plugin package must declare both dsh.bundle.patch and dsh.client.platform: "web" — a package with only dsh.client installs as a plain dependency and shows no UI.

Do favorites survive uninstalling the plugin?

They persist in your DSH profile. Reinstalling the plugin brings the list back. Uninstalling does not delete conversations or messages.

Are favorites shared between my devices?

They are stored in your DSH profile on the host, so every tab and browser using that profile sees the same list. Separate DSH installations keep separate lists.

Can I use it alongside other sidebar plugins?

Yes. The plugin only adds a footer entry, a header star, and an @ source. It does not modify DSH's source or take over any other plugin's UI.

If something else goes wrong, open an issue with your DSH and plugin versions, reproduction steps, and error details.

Install from source

Expand for development or testing unreleased changes

There is no build step: src is what ships, so the checkout runs as-is.

[Console]::OutputEncoding = [System.Text.Encoding]::UTF8
$OutputEncoding = [System.Text.Encoding]::UTF8

git clone https://github.com/hiuga0321/dsh-session-favorites.git
Set-Location .\dsh-session-favorites
dsh plugin --profile web add .

Restart DSH Web and hard-refresh your browser afterward.

Checks before publishing:

node scripts/smoke.mjs                    # package identity, client load, key interaction paths
node --test test/schema.test.mjs          # storage-domain record schema
node --test test/favorites-core.test.mjs  # favorites CRUD logic
node --test test/client.test.mjs          # client contracts across DSH versions

scripts/smoke.mjs enforces that four declarations agree — src/package-identity.js, package.json's name, cordis.patch.yml's name, and the client bundle's id. Renaming the package and missing one of them fails here.

devDependencies are pinned to 0.1.5-rc.2, the compatibility floor and the baseline for host/remote contract verification. To run a real version matrix, install each version separately and run the checks above against each — fixtures for both client contract shapes are already in place.

License

Licensed under the MIT License.