DeepSeek Harness Plugin Hub

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

探索

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

社区

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

相关链接

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

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

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

dsh-wo-tmux

Wo Tmux

Workspace Overview tmux 标签页:显示工作区的实时/冻结/冷却会话状态,通过 tmux-fridge 一键连接终端,提供冻结/快照/恢复操作,并为自定义会话名称提供明确的工作区到会话链接。

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

npx -y @deepseek-ai/dsh plugin --profile web add github:joao-paulo-santos/dsh-wo-tmux#9d4465f2ecd83d829757501c6b22aaccc63524cd
README兼容性版本

兼容性与来源证明

Wo Tmux 以 dsh-wo-tmux 发布,当前版本为 0.2.0。Plugin Hub 会校验它的 manifest,并保存精确安装来源,便于复现安装结果。

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

版本

0.2.0stable
2026/9/1
0.1.5stable
2026/9/1
0.1.4stable
2026/8/31
查看其余 2 个版本收起版本
0.1.3stable
2026/8/31
0.1.0stable
2026/8/31

相关插件

正在加载相关插件…

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

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

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

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

认领这个 Plugin →
报告问题

相关插件

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

Better Sidebardsh-better-sidebarDSH web 插件:类似 VSCode 的右侧边栏(资源管理器 / 编辑器 / 终端 / git / 浏览器),按对话会话隔离。提供服务,供其他插件注册侧边栏标签页和文件查看器。Find Plugindsh-find-plugin在代理中查找 DeepSeek Harness 插件——实时搜索 GitHub 上的 dsh-plugin 主题,并按星标数排序。DSCODE@toddzheng024/dscode-bundle完整的 DeepSeek 编码代理,支持持久化 shell、Ultra 协作和自动权限审查。Plugindsh-pluginDeepSeek Harness 社区插件市场,遵循官方插件规范——无需离开应用即可浏览、搜索并安装 9000+ 个由人工精选的社区插件。· DeepSeek Harness 社区插件市场(遵循官方开发规范):9000+ 人工精选社区插件,每日更新。

README

dsh-wo-tmux

A DeepSeek Harness (DSH) plugin: your tmux workflow, wired into the Workspace Overview tab. The plugin knows whether the current workspace's tmux session is live, frozen with tmux-fridge, or resting in cold storage, and one click opens a fresh terminal attached to it: unfreezing or recovering first when needed.

For people who live in named tmux sessions per project and suspend work mid-thought, this closes the gap between the browser harness and the console: no more tmux ls, no more remembering which projects are frozen.

What you get

  • Pill in the session header: shows the workspace's tmux session and its state; clicking opens a terminal attached to it (attach, unfreeze, or recover, per state). Hidden for workspaces without a session, or via a toggle in Granular Settings.
  • Tmux subtab in Workspace Overview, in two panes:
    • Session (default):
      • a status card: session name, state chip, how it was resolved (explicit link or name convention), attached clients and windows;
      • actions per state: open console, snapshot to cold storage, freeze (with a confirmation; freezing kills the live session), recover, clean snapshot (also confirmed);
      • linking: pin the workspace to any session name (grouped by live, frozen, cold storage), unlink, or create a new session (pre-filled with the workspace basename, auto-linked, opened in a terminal).
    • All sessions: every session the machine knows about, grouped by store: live sessions (open console, freeze, snapshot), frozen sessions (unfreeze), and cold-storage snapshots (recover, clean). Freezing any live session from this pane is how a project gets parked without leaving the harness.
    • The tab polls while it is open: after an action (unfreeze hands off to a terminal and returns before tmux settles) the state chips catch up on their own, no page switching needed.
  • Workspace-to-session links survive reboots in ~/.dsh/settings/wo-tmux.json, so colliding basenames (two projects named api) stay unambiguous.

How it resolves a workspace to a session

First match wins:

  1. an explicit link from the link store;
  2. a tmux session named like the workspace's basename, looked up in the live server, the frozen list, then cold storage;
  3. nothing (the tab invites you to create or link).

How it talks to tmux

The host half shells out to the tmux and tmux-fridge CLIs with argument arrays only (no shell interpolation). Open runs the fridge command bare: tmux-fridge detects and launches the terminal for the attach itself and exits, so wrapping it would only flash a window that dies the moment the handoff happens. Only create needs a terminal from us (plain tmux new-session cannot spawn one): $TERMINAL picks the emulator; without it the plugin probes kitty, alacritty, wezterm, gnome-terminal, x-terminal-emulator, and xterm, and detaches the session when none is found. The TMUX_FRIDGE_BIN environment variable overrides the fridge binary location. Storage formats are never read directly: the CLIs are the contract, so tmux-fridge can change its layout freely.

How to install

Requires a DeepSeek Harness checkout and a profile, here web. tmux and tmux-fridge must be on PATH. Clone the dependencies and this plugin into a plugins folder:

mkdir -p ~/dsh-plugins && cd ~/dsh-plugins
git clone https://github.com/joao-paulo-santos/dsh-workspace-overview.git
git clone https://github.com/joao-paulo-santos/dsh-wo-tmux.git

# from the harness checkout
pnpm dsh plugin --profile web add ~/dsh-plugins/dsh-workspace-overview
pnpm dsh plugin --profile web add ~/dsh-plugins/dsh-wo-tmux

# verify the profile still composes
pnpm dsh --profile web --dump-config

Restart the harness; the Tmux tab appears in Workspace Overview and the pill appears on sessions whose workspace has a session.

Dependencies

  • dsh-workspace-overview hosts the subtab and the pill (required; without it the client half stays inactive)
  • the tmux binary on PATH (session listing and creation)
  • the tmux-fridge binary on PATH (frozen/cold storage and the attach actions); without it the tab still shows live state and a clear "not on PATH" note
  • a terminal emulator: $TERMINAL or one of the probed ones; without any, open and create fall back to detached sessions where possible

Plugins dependent on this

(none)

Limitations

  • The plugin never embeds a terminal in the browser; it spawns a real terminal window. That is the point.
  • One terminal window per click. Attaching twice to the same session is normal tmux and stays your business.
  • Name detection covers one session per workspace; many-to-many setups (several sessions for one project) are out of scope, though linking picks the one you care about.