Skip to main content

Deepseek-Harness-Desktop/vendor/deepseek-harness/packages/bundle/web-app

127Stars9Forks0Issues0Watchers

dsh Web layer package: mounts Web host, Web server, API gateway, browser plugin manifest, and frontend static fallback on base; provides dsh --profile web CLI argument parsing and startup URL output

Evidence5/5methodologySourceInstallMaintenanceDSH versionSecurity scan
Machine-auditedInstall commandRepo verifieddsh-plugin topicLicenseREADMEAI wiki

ⓘ This plugin is a sub-package of the ChisaAlter/Deepseek-Harness-Desktop monorepo — stars and activity count the whole repository.

Language
JavaScript
License
MIT
Branch
main
deepseekdeepseek-harnessdsh-plugin

Install

cmdweb profile
$ dsh plugin --profile web add @deepseek-ai/dsh-web-app

Run the command above in your terminal to install this plugin via the dsh CLI. You can switch Profile in the top-right corner. New to dsh? Read the beginner tutorial

Install via your agent

Install the DeepSeek Harness plugin ChisaAlter/Deepseek-Harness-Desktop/vendor/deepseek-harness/packages/bundle/web-app for me: review the repository at https://github.com/ChisaAlter/Deepseek-Harness-Desktop first, then run the install command and verify the plugin loads successfully.

Paste this instruction to the DSH Web GUI assistant — it will install and verify for you.

This document corresponds to the sub-path vendor/deepseek-harness/packages/bundle/web-app in the vendor repository and serves as the content source for the Plugin Encyclopedia module on the landing page /plugins/{owner}/{repo}.

One-Line Positioning

@deepseek-ai/dsh-web-app is DSH's browser surface bundle: it mounts a Web server, API gateway, workspace, projection cache, storage, browser plugin manifest, and frontend dist fallback on top of dsh-base, with the built-in web-runtime glue plugin parsing build artifacts, registering web surface prompts with the model, injecting the DSH_WEB_URL bash variable, and printing the dsh web: URL line.

Core Capabilities

  • Covers host runtime required for the Web surface above dsh-base: Web server, API gateway, workspace, projection cache, JSON/domain storage, message feedback, directory selector, plugin/MCP/skill inventory
  • Mounts browser-side plugin manifest (~40 dsh.client lines) and a permanently mounted idle client HMR listener chain (idle while waiting for client bundle rewrite during pnpm run dev:web)
  • Provides dsh --profile web command-line parsing: parses --host, --port, repeatable --trusted-host and --help, rejecting --host 0.0.0.0 and non-numeric ports
  • Parses the built frontend dist (@deepseek-ai/dsh-web-frontend/dist/index.html) and mounts the frontend-static fallback
  • Samples a one-time LAN trust snapshot after binding, providing it as webRuntime service to browser trust barrier and UI endpoint
  • Registers app:web-surface system prompt segment and DSH_WEB_URL managed bash environment variable, enabling the model to recognize "this GUI" and what "this page" refers to
  • Prints dsh web: http://127.0.0.1:<port> URL line after Loader configuration tree settles; includes LAN URL when bound host is full network card
  • Explicitly disables agent-plane tool rows (bash / pwsh / fs / skill / subagent / workflow / todo / web / goal / plan / compact etc.), leaving these capabilities to be mounted by agent presets on demand per session

Technical Implementation

  • Language: TypeScript (ESM, package declares "type": "module", three entry files: src/index.ts web-runtime glue plugin + src/startup.ts command-line provider + src/invariant.ts invariant companion)
  • Key Dependencies: @deepseek-ai/cordis (peer, host runtime), @deepseek-ai/cordis-plugin-loader (peer, profile loading), @deepseek-ai/dsh-system-prompt (peer, prompt registration), @deepseek-ai/dsh-shell-env (peer, managed bash variable); actual patches read by the combiner
  • Architecture Pattern: Profile bundle - cordis.patch.yml exposes via manifest field dsh.bundle.patch, read by profile combiner and inserted line by line; package also mounts two Cordis runtime plugins: web-startup (regular service plugin, parses CLI and publishes webStartup) and web-app (depends on webServer and webStartup, publishes webRuntime)
  • Entry Files: src/index.ts:135 (apply(), web-runtime glue logic) / src/startup.ts:65 (apply(), commander command-line parsing) / cordis.patch.yml:1-473 (~60+ lines of patch list, actual product payload)

Applicable Scenarios

When users want to run the DSH official browser interface (the GUI from dsh web) on their own machine, they need to install this bundle along with dsh-base into the profile: it provides Web server, API gateway, workspace, persistence, client plugin manifest, and startup URL output, serving as the essential layering that exposes dsh-base's basic capabilities in browser interaction form; if they just want to run a one-time task without opening the GUI, they should use the adjacent dsh-headless profile instead, which doesn't mount this bundle.

Prerequisites and Compatibility

DependencyMinimum VersionDescription
DSH0.1.0-rc.6+Package version aligns with upstream baseline 0.1.0-rc.7; peers include @deepseek-ai/cordis @deepseek-ai/cordis-plugin-loader @deepseek-ai/dsh-shell-env @deepseek-ai/dsh-invariants @deepseek-ai/dsh-system-prompt must be available in host
Node>=22.19.0From upstream monorepo engines.node: `^22.19.0
PlatformmacOS / Windows / LinuxPatch has no platform branches, same copy across platforms; CLI parsing leaves port and host validation to commander
Native ModulesNoneThis package doesn't directly import native dependencies; lower-layer bundles use node:sqlite (full-text search, off by default) and node-pty from other bundles / desktop shells

Installation

dsh plugin --profile web add github:ChisaAlter/Deepseek-Harness-Desktop/vendor/deepseek-harness/packages/bundle/web-app

Configuration

Three Configs declared by the web-runtime glue plugin (src/index.ts) (assigned by cordis.patch.yml top-level):

ConfigTypeDescriptionDefault
printUrlbooleanWhether to print dsh web: http://127.0.0.1:<port> after startup once Loader config tree settles (includes LAN URL when bound to full network card). Non-interactive callers can turn offtrue
surfaceContextbooleanWhether to register app:web-surface system prompt segment and DSH_WEB_URL managed bash variable; non-GUI callers can turn off to prevent model from misreading contexttrue
trustedHostsstring arrayExplicit --trusted-host list (hosts or host:port appended to /api browser trust barrier), stacked in CLI argument order[]

Four flags parsed by command-line (src/startup.ts), directly accepted by dsh --profile web:

FlagDescription
--host <host>Binding host; for security, 0.0.0.0 is explicitly rejected
--port <port>Listening port; 0 lets OS pick an available port; non-numeric throws error immediately
--trusted-host <authority...>Repeatable, appends host or host:port to /api browser trust barrier
-h, --helpPrints help and exits with code 0; in this mode does not publish webStartup, so server won't start

The patch also contains a set of static default values (session-query-sqlite.path: ':memory:', message-feedback.maxNoteBytes: 8192, session-projection-cache.writeEveryEvents: 200 and writeIntervalMs: 5000, tool mode takes env var DSH_TOOLS_MODE, agent-presets.default: standard etc.), which are patch-built-in configurations, not separate user-facing config entries.

FAQ

Q: After installing this bundle, will I get the dsh --profile web browser interface?

A: Yes. The patch mounts webserver, API gateway, workspace, projection cache, storage, browser plugin manifest, and frontend dist fallback, then the web-runtime glue plugin parses build artifacts and prints the dsh web: http://127.0.0.1:3080 URL line.

Q: Do I need to build the frontend dist separately before using it?

A: Yes. The runtime glue plugin locates the dist via require.resolve('@deepseek-ai/dsh-web-frontend/dist/index.html'); if not built, it throws an error directly during activation and prompts to run pnpm run build first, with no fallback to serve from source.

Q: After startup, I want to change port or restrict access to specific hosts only. How should I write it?

A: Use CLI flags: dsh --profile web --port 8080 --host 127.0.0.1, repeatable --trusted-host app.internal to add hostname/IP to /api browser trust barrier; these are parsed by web-startup line during loading phase, not written into patch.

Q: What's the relationship between this bundle and dsh-base?

A: Required layering: base is the common foundation for any profile (model, tools, sandbox, telemetry, persistence), web-app inserts Web-specific host runtime on top of base (webserver, api-gateway, storage, workspace), command-line, and browser plugin manifest, while disabling the agent-plane tool rows from base that will be taken over by agent preset.

Q: Why is --host 0.0.0.0 not allowed?

A: The CLI explicitly rejects this value before publishing webStartup to avoid binding full network card and exposing code execution capability to the entire network; use --host 127.0.0.1 or a specific LAN IP instead.

Q: After startup I can't access the page on LAN IP in browser. What should I do?

A: Add the corresponding LAN network card IP to --trusted-host; both browser trust barrier and UI-listed LAN URL use the same snapshot. Changes are sampled only once at startup; network card changes during runtime won't be re-announced.

Q: Where did the bash / fs / skill tools used by Agent go?

A: These agent-plane tool rows are explicitly disabled: true in the patch, because they're now mounted on demand by agent preset per session. Base's process-level services (shell-env, subagent registry, target service, remote /api gateway, etc.) remain on the host plane and continue to be used by the web surface.

Learning Curve

Beginner — just add it to --profile web to get the official GUI; port/host/trust source changes all use existing CLI flags, no patch modification needed.

Known Issues and Limitations

  • Frontend dist must be built first: The runtime glue plugin locates dist via require.resolve('@deepseek-ai/dsh-web-frontend/dist/index.html') at activation; unbuilt throws error directly and prompts to run pnpm run build first, no fallback to serve from source
  • lanAddresses is a startup snapshot: Network card changes after binding won't be re-announced; printed LAN URL always matches configured trust barrier, requires restart for changes to take effect
  • --host 0.0.0.0 not supported: CLI explicitly rejects before publishing webStartup to avoid exposing RCE capability to entire network; currently not supporting binding all network cards is intentional
  • Shared HMR not yet enabled: The hmr line in patch is disabled: true with TODO marker ("Re-enable shared HMR for Web after its reload lifecycle is tested"); currently client-hmr is a permanent idle chain, only triggers hot-reload when running pnpm run dev:web in same checkout
  • Without trusted-hosts configured, only local machine is trusted: Default --trusted-host is empty, host is 127.0.0.1, so LAN/public access will be rejected by /api browser trust barrier, needs explicit declaration to open

Read the usage guide →

Install steps, key points, FAQ and compatibility for this plugin — auto-derived from indexed fields.

Listing badge

Listed on deepseek-plugin.org
[![Listed on deepseek-plugin.org](https://img.shields.io/badge/listed_on-deepseek--plugin.org-007EC6)](https://deepseek-plugin.org/plugins/ChisaAlter/Deepseek-Harness-Desktop/vendor/deepseek-harness/packages/bundle/web-app)

Paste this markdown into your GitHub README to link back to this listing. The badge only states the listing — not a security endorsement.

← Back to plugin directory