DeepSeek Harness 插件

dsh-widescreen

Widescreen mode for the DeepSeek Harness session detail page: a General-settings toggle that lets the chat use the full browser width instead of the fixed 748px content column.(英文原文)

跳到安装方式

来源信息

GitHub 仓库
Temoa/dsh-widescreen
最近更新
2026年8月15日
分类
工具与能力
GitHub stars
0
载体类型
plugin
目录证据
上游声明已找到 dsh.bundle
证据路径
package.json#dsh.bundle
核对版本
0.1.0-rc.8
上游核对日期
2026-08-20

该证据由上游目录提供。本站没有安装、运行或安全审核这个插件。

安装

默认先复制一段 Prompt,让 Agent 读 GitHub 仓库和源码;需要自己装时再切到命令。

复制这段 Prompt,发给 DSH、Codex 或其他 Agent,让它先读 GitHub 仓库和源码。

请先不要安装或执行任何命令。阅读这个插件的 GitHub 仓库、README 和关键源码,然后用清楚、直接的方式回答以下问题,帮助我判断它是否适合我的需求:

1. 这个插件是什么,解决什么问题;
2. 适合哪些用户和典型使用场景;
3. 安装后如何使用,并给出一个最小使用示例;
4. 有哪些已知限制,以及隐私、安全、兼容性或维护风险;
5. 给出“推荐 / 有条件推荐 / 不推荐”的明确建议和理由。

请区分仓库明确说明、根据源码推断和未知信息。证据不足时请明确说明,不要猜测或照抄 README。

GitHub:https://github.com/Temoa/dsh-widescreen
插件名:dsh-widescreen
作者:Temoa

检查来源文件

安装前先看这个插件目录里的 README 和其他文件。

文件资源管理器3 个文件
README.md来源说明 · 只读预览

dsh-widescreen

Widescreen mode for the DeepSeek Harness web UI. Adds a toggle in Settings → General (设置 → 通用设置) that lets the session detail page fill the available browser width instead of the fixed 748px content column.

Features

  • One switch in Settings → General: Widescreen mode (宽屏模式).
  • When on, the chat column, date dividers, question cards, and the composer card all expand to the full width of the center column — no more excessive whitespace on wide monitors.
  • When off, behavior is byte-for-byte the shipped default (748px content column).
  • Container-relative sizing only (--dsh-chat-content-width: 100%): browser zoom and window resizing keep reflowing exactly as before, and narrow viewports are unaffected.
  • The preference is persisted in the DSH user-settings document; it survives page reloads and restarts.
  • Fully reversible: removing the plugin restores the default layout with no residue.

Install

> Requires DSH 0.1.0-rc.x (Web profile).

From GitHub

dsh plugin --profile web add github:Temoa/dsh-widescreen

No build scripts are involved: the repository ships pre-built lib/ artifacts, so no prepare authorization is needed.

From a local checkout

dsh plugin --profile web add ./dsh-widescreen

Restart dsh after installing (dsh --profile web), then open Settings → General and flip the switch.

Uninstall

dsh plugin --profile web remove dsh-widescreen

Restart dsh after removing (dsh --profile web). The default 748px layout is fully restored: the stylesheet and the <html> attribute are torn down with the plugin, and the persisted preference section is ignored once the namespace is gone.

How it works

The conversation root in dsh-client-ui-conversation pins the chat content width with a component-scoped CSS variable:

--dsh-chat-content-width: 748px;

Every width-limited element (chat column, date dividers, user-question cards, composer card, dock rows) reads that variable. The plugin:

1. Registers a durable widescreen settings namespace on the Host (lib/index.js). 2. Binds it on the client through ctx.settingsScope and keeps a snapshot store in sync (lib/client.js). 3. Injects a small stylesheet and toggles an data-dsh-widescreen attribute on <html>. The stylesheet redefines the variable to 100% on the two containers that own every consumer:

html[data-dsh-widescreen="on"] [data-conversation-scroll],
html[data-dsh-widescreen="on"] [data-composer-seat] {
  --dsh-chat-content-width: 100%;
}

--dsh-composer-card-max-width derives from the same variable, so the composer follows automatically. Because the value is container-relative (100%), the original viewport/zoom-responsive reflow is untouched.

The General-settings row registers into the additive settings.general.item slot (order 30, after Appearance and Composer Enter), exactly like the shipped preference rows.

Repository layout

dsh-widescreen/
├── package.json        # dsh.bundle.patch + dsh.client manifests
├── cordis.patch.yml    # composition layer: inserts the plugin row
├── lib/
│   ├── index.js        # Host half: settings namespace registration
│   └── client.js       # Browser half: __ModuleLoader__ bundle
├── README.md
├── README.zh.md
└── LICENSE

The client bundle is authored directly in the official window.__ModuleLoader__.load({ id, factory }) artifact format documented in the harness's client build tooling, so the repository needs no build step to install.

Development

npm run check   # node --check on both lib files

License

[MIT](LICENSE)