DSH Plugins Marketplace

DSH Plugins

Plugins

/

Tools & Capabilities

/

dsh-plugin-cookie-whitelist

d

dsh-plugin-cookie-whitelist

Manifest valid

Gives the agent your browser login state only for domains you approve: a Chromium/Firefox extension filters cookies to the approved list before they leave the browser, a token-gated 127.0.0.1 receiver

UI (client)hasBundlePatch

dsh-plugin-cookie-whitelist

Give the agent your login state only for domains you approve — with a browser extension, a localhost receiver, an in-memory vault, and a read-only CDP browser.

This plugin lets DeepSeek Harness read pages that need your browser session. Cookies are read inside Chrome, Edge, or Firefox by an extension, filtered to an approved domain list before they leave the browser, posted to 127.0.0.1 with a pairing token, and kept only in Host process memory. The agent then uses a disposable incognito Chrome/Edge instance that receives cookies for the current whitelisted domain only.

At a glance

  • Extension side — Chromium Manifest V3 and Firefox Manifest V2 share one background.js; the only network destination is http://127.0.0.1:<port>.
  • Host side — token-gated receiver, per-domain authorization requests, in-memory vault with TTL, read-only browser, optional interactive login fallback, and a settings page.
  • Read-only by construction — form submit, requestSubmit, window.open, and every non-GET/HEAD/OPTIONS request are blocked. There is no fill tool.
  • No cookie persistence — values are never written to disk, logs, tool results, or the settings UI. The browser profile is disposable and incognito.

Install

  1. Install the DSH plugin:

    dsh plugin --profile desktop add github:wth373737/dsh-plugin-cookie-whitelist
    

    or use Plugins → + Add plugin, or plugin_manager's install_bundle against a local checkout while developing.

  2. Open Settings → Cookie Whitelist; copy the receiver URL and pairing token.

  3. Load the extension:

    • Chrome/Edge: chrome://extensions → Developer mode → Load unpacked → extension/chromium.
    • Firefox: about:debugging → This Firefox → Load Temporary Add-on → extension/firefox/manifest.json.
  4. Paste the URL and token into the extension options; click Test connection.

  5. Add domains in the settings page, or let the agent call cookie_authorize and approve it in chat.

For browsers without a supported extension, use the settings page's Temporary browser login window: it opens a disposable incognito Chrome/Edge window, the user logs in by hand, and Finish and capture copies the domain's cookies into the vault.

Until one of those two paths is in place the plugin accepts no cookies, so cookie_browse visits every site anonymously.

Tools

ToolPurpose
cookie_whitelist_statusWhitelist, pending requests, extension heartbeat, vault counts, browser state. Never returns values.
cookie_authorizeAsk the user to approve one domain; approval is a user action.
cookie_syncAsk the extension to re-read approved domains; counts only.
cookie_browseRead-only open / read / snapshot / click / scroll / screenshot / files / read_file / status / close.

Files and Course Planner

Course pages often put test dates, schedules, rubrics, and guidelines in files rather than page text. Use:

cookie_browse { action: "files" }
cookie_browse { action: "read_file", url: "<mod/resource link>" }

read_file downloads with whitelist cookies only, follows an HTML resource wrapper to a preferred Course Planner / Schedule / Syllabus / Teaching Plan PDF, and extracts PDF text with pdfjs-dist. Files above the default 8 MB limit trigger a chat approval. Nothing is kept by default; ask before using keep: true. This matters: in CMT221W the Test 1 date appears only in the Course Planner PDF.

Security model

  • The receiver binds 127.0.0.1 only and requires the pairing token on every /v1/* call.
  • A request whose Origin is an ordinary http(s) page is rejected; only extension origins and local header-bearing calls pass.
  • Cookies are accepted only when the cookie's own Domain applies to the requested whitelisted domain; the Host re-filters every delivery.
  • Before each navigation the browser jar is cleared, then only cookies whose domain matches the whitelisted target are injected.
  • Non-whitelisted top-level pages have the Cookie header stripped from every intercepted request.
  • The extension's <all_urls> permission is required by the cookies API; it has no content scripts, no telemetry, and no remote endpoint.

See SECURITY.md and docs/ARCHITECTURE.md for the full threat model.

Known limits

  • Some sites reject cloned sessions (device binding, risk controls); the mechanism is not a guarantee.
  • CAPTCHA/2FA requires the user; the temporary login window is the fallback.
  • Firefox needs a temporary or signed add-on; Chrome/Edge use developer-mode unpacked loading.
  • Chrome/Edge forbid remote debugging on the default profile, so an isolated profile is used intentionally.
  • Screenshots can contain personal data; if the attachments service is unavailable the PNG is written to the plugin's shots/ directory.

Development

node scripts/build-extensions.mjs
node test/smoke.mjs
node test/file-reader.mjs
node test/extension-sim.mjs
node test/browser.mjs       # requires Chrome/Edge; launches a disposable instance
node test/host-sim.mjs

License

MIT. Original icons. The Host half depends on pdfjs-dist for PDF text extraction; the browser extension has no third-party runtime.

Comments

Loading…

Similar plugins

dsh-chrome-use

by tao1020

Codex-style browser control: drives your own Chrome through a local bridge, so the model can read pages, click, fill inputs, scroll, take screenshots, and inspect console and network logs. Requires Ch

Tools & CapabilitiesManifest valid

★ 13

↓ 1.4k/wk

MIT

JavaScript

Nov 19, 2026

dsh plugin --profile web add dsh-chrome-use

by L1818346

Browser takeover for sign-in-gated sites: keeps a list of addresses that need a login (URL and date only, no credentials), answers before a visit whether an address is already on it, reports whether t

Tools & CapabilitiesManifest valid

★ 0

MIT

JavaScript

Oct 31, 2026

dsh plugin --profile web add dsh-browser-takeover

by chaserchan

DSH plugin: drive a real Chrome from your dsh agent via the browser-use Browser Harness (local, no API key).

Development & InfrastructureTerminal & ClientsManifest valid

★ 0

MIT

JavaScript

Sep 25, 2026

dsh plugin --profile web add dsh-browser-harness

by dougen

Drives a Chromium browser you are already running — Chrome, Edge, Brave, Vivaldi, Opera, Chromium, Arc or Thorium — over one long-lived CDP connection, so the remote-debugging approval is asked once i

Tools & CapabilitiesManifest valid

★ 0

JavaScript

Nov 17, 2026

dsh plugin --profile web add @dougen/dsh-cdp

by ZSeven-W

DeepSeek Harness plugin for browser automation, headless first. Every agent gets its own throwaway Chrome/Edge/Chromium profile, short-lived semantic references instead of CSS selectors, scoped subtre

Development & InfrastructureManifest valid

★ 9

↓ 102/wk

MIT

JavaScript

Sep 24, 2026

dsh plugin --profile web add @zseven-w/dsh-browser

by KasenRi

Controlled browser automation for DeepSeek Harness: the agent_browser tool and BrowserAutomationService drive a real Chromium or Chrome page (or an explicit CDP endpoint) through the agent-browser CLI

Tools & CapabilitiesDevelopment & InfrastructureManifest valid

★ 0

MIT

JavaScript

Sep 19, 2026

dsh plugin --profile web add @kasenri/dsh-browser