dsh-gui-browser
GUI 右侧边栏中 Session 内置 Chromium 的可操作实时视图，并将查看者的输入反馈给模型
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add github:shittass/dsh-gui-browser#4ba29860e5c303dd96845f17f64c322c8bec1ab5Gui Browser 以 dsh-gui-browser 发布，当前版本为 2.1.0。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
点击下方 Badge 复制 Markdown，粘贴到 README 即可。
验证 package.json 声明的 GitHub 仓库，即可管理这个公开页面。认领后，Hub 会优先安排当前版本的安全扫描，并在通过后公开展示结果。
认领这个 Plugin →An operable, live view of the Session's built-in Chromium in the GUI right
Sidebar — the same browser the model's mcp__playwright-mcp__* tools drive.
engines.dsh and the
@deepseek-ai/dsh-* peers — so the plugin manager refuses the install on an
older runtime and boot denies this row instead of failing halfway through;
dsh plugin allow-version is the deliberate, per-version override.^22.19 || >=24.@deepseek-ai/dsh-base and @deepseek-ai/dsh-web-app:
the pane is a Web right-Sidebar tab.@deepseek-ai/dsh-browser-use and
@deepseek-ai/dsh-experimental-browser-use-playwright-mcp) so the provider rows
resolve, and its patch overrides the Playwright MCP provider's row to point it
at the launcher — but the rows themselves, and the isolated headless Chromium
behind them, come from a browser-use bundle enabled earlier in the layer order
(this repository's sibling dsh-browser-use-playwright is exactly those two
rows). A profile admits one provider at a time: @deepseek-ai/dsh-browser-use
owns the single registration slot and rejects a second one, so never enable two.
Without any, the pane stays in its idle state and says so.dsh plugin --profile <profile> add dsh-gui-browser
dsh --profile <profile> --dump-config # the layer is listed as dsh-gui-browser
The package's postinstall (launcher/install.mjs) puts the platform launcher
in the registry directory; see The launcher. pnpm ≥10 runs no
dependency lifecycle script until it is allowed, so the install reports a pending
build script and the plugin manager asks for it — approve it, because without
that step there is no launcher.sh/launcher.exe for the provider to launch.
The step is idempotent and never fails an install: on a machine with no C#
compiler it warns loudly and leaves the Windows launcher absent rather than
breaking the package.
dsh plugin --profile <profile> remove dsh-gui-browser removes the dependency
and its layer.
Installing into a running Harness needs a restart. The plugin manager tries
to activate a newly installed bundle through HMR, but a Host answers plugin
specifiers from the package table it built at startup: a package name it has not
seen before is reported as failed to import and mounts only after a restart
(measured — the same process imports a pre-boot name, and the resolution a fresh
boot computes points at the right directory). The pane then appears on its own,
and the browser it mirrors keeps running across the restart because the browser's
debugging port is recorded in the registry directory rather than held by the
plugin. Replacing a package in place has the same requirement.
To publish from a checkout, npm pack builds the tarball; its contents are
exactly files in package.json — sources, the launcher's .cs/.mjs/.sh,
and never a compiled binary.
--remote-debugging-port, added by wrapper.sh)
and pushes Page.startScreencast frames of the page target. Nothing is
re-rendered, re-laid-out, or resized: the viewport, the page state, and the
focus are whatever the browser has. One thing is corrected: a page Chromium
created on its own (the new tab after a browser's last page closes, or a popup
a site opened) is born at Chromium's unsized 800x600 default, which is narrower
than most pages and arrives cropped, so any page still at exactly that size is
set to the browser's own viewport (1280x720). Any other size — the model's own
resize, a site's popup size — is left alone.about:blank and named a moment later — takes
the view, and a page chosen by hand from the page menu keeps it until another
page appears or that one closes.+ opens a new tab page and puts the cursor
in the address bar; the strip scrolls sideways with the wheel. The address bar
shows the shown page's URL and can be typed into — a scheme is taken at its
word, a bare host gets https://, and anything else becomes a Bing search, the
same three-way guess Chrome makes. Everything the pane does to a page is
reported to the model; the frame-quality rows in the ⋮ menu are the viewer's
own preference and are not.index=0/0), so Back there restores the page the
link was clicked from instead of doing nothing. Alt+Left and Alt+Right are the
same two actions while the pane has focus, and the toolbar dims a direction
that would do nothing.Loopback callers only.
| Route | Meaning |
|---|---|
GET /gui-browser/list | every live browser's state |
GET /gui-browser/status?port= | one browser's state |
GET /gui-browser/frame.jpg?port= | newest frame as a still image |
GET /gui-browser/activity?session= | the exact text the model would receive |
GET /gui-browser/stream?port= | MJPEG fallback for a non-WebSocket viewer |
POST /gui-browser/input?port=&session= | the same commands the socket takes |
WS /gui-browser/ws | frames and state downstream; input, caret, page choice, frame quality, and pane visibility upstream |
host.js — stable entry; imports engine.js?rev=<mtime> so a Host-process
module cache cannot pin an old generation for the life of the process.engine.js — registry watcher, CDP plumbing, WebSocket transport, input
translation, and the model-facing activity record.client.js — the gui-browser right-Sidebar tab: canvas view, socket,
pointer/keyboard/IME handling, zoom, auto-open.wrapper.sh — the POSIX Chromium launcher: allocates a free debugging port per
launch and publishes it under ~/.dsh/run/gui-browser/.launcher/launcher.cs, launcher/install.mjs — the same launcher for Windows
and the install step that puts either one in place.Playwright is pointed at a launcher through the provider's executablePath,
because that is the only hook a bundle has for adding --remote-debugging-port
beside Playwright's own control channel. The patch names it as
dshHomePath('run', 'gui-browser', 'launcher.exe' | 'launcher.sh'), so it never
has to know where the package was installed, and the bundle's postinstall
(launcher/install.mjs) puts the right launcher for the platform in that
directory:
wrapper.sh copied to launcher.sh, mode 755.launcher.cs compiled to launcher.exe by the csc.exe that every
.NET Framework install provides, with PowerShell Add-Type as the fallback.
Nothing prebuilt ships in the package, so there is nothing to sign or build per
architecture; a machine with no C# compiler is reported loudly and otherwise
ignored, and the model keeps its browser either way.Two things about the Windows launcher are load-bearing. Playwright spawns
executablePath without a shell, so a .cmd cannot be used at all
(spawn EINVAL); and it hands the browser its DevTools pipe as CRT file
descriptors 3 and 4, which Windows passes in STARTUPINFO.lpReserved2 — a
per-process descriptor table the child's CRT reads at startup. The launcher
therefore calls CreateProcess itself, forwards that block unchanged, and marks
the handles it names inheritable; Process.Start would lose the block and
Chromium would refuse to start with "Remote debugging pipe file descriptors are
not open". launcher.exe --gui-browser-handles prints the inherited table, which
is how that failure is told apart from a broken browser.
Ctrl+wheel (page zoom) is not forwarded: it would desync the pane's geometry from the browser's viewport.
A browser showing this GUI itself is view-only, so the nested panel cannot forward its own clicks forever.
The viewer's clipboard reaches the page on paste, and the page's selection reaches the viewer on Ctrl+C; richer clipboard flavours are not bridged.
Chromium's frame pacing is left alone by default. Measured here: the default
60 Hz frame clock gives 60 fps repaint, 59.3 fps capture, 60 fps delivery with
no dropped frames — the pipeline is not the limit, the frame clock is.
--disable-frame-rate-limit --disable-gpu-vsync raises capture to ~114 fps but
drives requestAnimationFrame to ~3240 Hz, changing every animation's timing
for the model as well. To opt in for the next launch, create a file named
uncapped in the registry directory (~/.dsh/run/gui-browser/); delete it to
go back. Page restarts are needed, so the browser's current tabs are lost.
Lossless frames are a per-viewer choice, off by default, because they cost the frame rate the pane exists for. Measured at 1280x720 on bilibili while it is being scrolled and repainted, from the browser's own process tree:
| encoding | frames/s | KB/frame | Mbit/s | cores |
|---|---|---|---|---|
| JPEG 88 (default) | 55.1 | 184 | 83 | 1.17 |
| JPEG 100 | 52.3 | 485 | 208 | 1.75 |
| PNG (lossless) | 17.5 | 768 | 110 | 1.84 |
A static page emits no frames at all in either mode, and the model's own screenshots are a separate on-demand capture: at the same moment a full-quality screenshot of that page measured 203 KB as JPEG and 654 KB as PNG, so the mirror's encoding never touches what the model sees. Those figures are for a full-size cast; because the cast now follows the pane, lossless costs a narrow pane far less than the table suggests — measured the same way, a 160x90 screencast held 60 fps at 2 KB a frame and 1.2 Mbit/s.
type"...", keys, scrolls, navigation) enriched with the
page's URL, title, and focused element, and contributed as one runtime-context
line to that Session's next model step.