DSH Marketplace

dsh-browser

Lum1104/dsh-browser

Chrome sidebar extension that lets DSH operate your browser directly, no vision capabilities required.

19714TypeScriptMITSource

Install

Add dsh-browser to DeepSeek Harness

via GitHub · GitHub source

Installing from GitHub runs the project's build script, which pnpm blocks until you allowlist it — run the command once and pnpm prints the exact key to add under `allowBuilds` in ~/.dsh/profiles/web/pnpm-workspace.yaml.

Due diligence

Before you install dsh-browser

  • Source of record: Lum1104/dsh-browser — present in the community registry that DSH's own plugin market installs from.
  • Licensed under MIT.
  • Detected: terminal surface. Read the source before granting these.
  • A listing here is not a security review. Plugins run with your agent's permissions.

What dsh-browser does

Structured page data flows through an authenticated bridge into numbered controls and returns as browser actions.

dsh-browser is a DeepSeek Harness plugin that connects DSH to a Chrome tab you already use, allowing the agent to read pages and operate their controls without visual input. It combines a browser bridge with a Chrome MV3 extension and exposes tools including browser_snapshot, browser_click, browser_type, browser_press, browser_scroll, navigation commands, browser_get_text, and browser_wait.

The extension turns a page into structured text containing its title, URL, main text, numbered interactive elements, and masked form fields. The agent addresses controls by number; screenshots are not sent through the model-facing pipeline. The bridge is registered in DSH’s local web profile, with the managed installation under ~/.dsh/dsh-browser and the extension under ~/.dsh/browser-extension. Local discovery uses /ext/bridge-config.

This is for browser tasks that depend on an existing login, session, or cookie state. It is not suitable for chrome:// pages, the Chrome Web Store, or workflows requiring screenshots or visual interpretation. The terminal surface includes shell-based installation and startup, while the browser surface reaches the selected Chrome tab: it can navigate, click controls, fill forms, and submit actions with the agent’s browser access. Password and payment-card values are masked before page data reaches the model.

dsh-browser documentation

How it behaves

dsh-browser controls the Chrome tab selected through its extension. browser_snapshot returns the page title, URL, main text, numbered controls, and masked form fields; delta: true returns only changes. browser_get_text reads a page region, including lazy-loaded or partial text. browser_click, browser_type, and browser_press operate controls and keyboard input. For browser_type, replace clears the field first. browser_scroll accepts viewport directions including up, down, top, and bottom. Navigation is provided by browser_navigate, browser_back, browser_forward, and browser_reload; browser_wait waits for page loading and rendering to settle.

Configuration and runtime

For local use, the extension discovers DSH through /ext/bridge-config. Loopback connections do not require a bridge token. DSH registers the bridge bundle in its local web profile and loads that profile at startup, so an already-running instance must be restarted after installation or an update. The default local address is http://127.0.0.1:3080. Remote deployment with --host 0.0.0.0 requires an address and bridge token.

Commands and paths

Start a managed checkout with pnpm start from ~/.dsh/dsh-browser, or start a cloned checkout with pnpm start from its repository root. The public release can be started with npx @deepseek-ai/dsh web. Both use port 3080 by default; --port <port> selects another port. The managed source is kept at ~/.dsh/dsh-browser; the built extension is copied to ~/.dsh/browser-extension.

Requirements and limits

The documented prerequisites are Node.js ^22.19 or >=24, Corepack/pnpm, and Google Chrome. The extension operates on normal http:// and https:// pages. Chrome-internal and protected pages, including chrome:// and the Chrome Web Store, cannot be read or operated. Password and payment-card values are rendered as •••• and do not enter the model-facing page data.

Written from the project's own documentation and kept in sync with it. Where the two disagree, the source is authoritative — read the README on GitHub

Same category

Alternatives to dsh-browser

treg

superdesigndev

425

Tool catalog for agents: search ~2,600 external endpoints (SEO and SERP, backlinks, social, people and company enrichment, ad libraries, scraping) by the task you want done, read each one's parameters and per-call price, then call it with the credential injected server-side. Ships the skill plus an MCP row that stays disabled until TREG_TOKEN is set.

npm packagePythontoday

notes

zhaoolee

142

Export DSH conversations as Smartisan Notes-style PNGs, or create and update Markdown notes in a configured account-scoped workspace.

GitHub sourceTypeScriptyesterday

modsearch

liustack

111

Web search bridge for text-only agents: ask the web or X, get structured JSON evidence (search, fetch, citations).

npm packageTypeScripttoday

argo

taxueseek

91

Search built for agents: multilingual coverage across web, academic, code, shopping, finance, news, and encyclopedias.

npm packagePython3d ago

ru-marketplace-mcp

Vladimir-Human

63

Skills and optional MCP rows for ten Russian marketplaces: price comparison across Wildberries, Detsky Mir and Yandex Market, plus per-source search, product cards and reviews. The 13 skills load on install; both MCP rows stay disabled until RU_MARKETPLACE_MCP_DIR points at a local clone, which needs Python 3.12+ and uv.

No one-line install — this plugin lives inside a larger repository and publishes no npm package.

GitHub sourcePythontoday
50

Undo/redo & rollback system for DSH: every config change is auto-snapshotted; undo/redo/restore to any version from the WebUI or the offline CLI/GUI tools (works even when DSH fails to boot).

npm packageJavaScripttoday