dsh-browser-scope

---

[!IMPORTANT] This is an independent community plugin. It is not published, maintained, or endorsed by DeepSeek, and it does not modify DeepSeek Harness core packages.
This plugin is still under development; if you encounter any bugs or unexpected issues, please report them to the developer via the issue tracker.

If it's useful, please stars let more people can see it~ Thanks♪(･ω･)ﾉ

Overview

What is the biggest pain point in frontend debugging? Invisible DOM trees, missed request details, inability to step through code, and error messages reduced to a single cryptic line. When autonomous agents encounter complex web issues, it's even worse — they are often stuck taking superficial screenshots, guessing causes, and repeating futile "refresh and retry" loops.

BrowserScope fundamentally changes this dynamic. It embeds a comprehensive Chromium workbench into the right sidebar of DSH Web, powered by 30 purpose-built automation tools. Agents can now directly inspect DOM nodes, interact with elements, review console logs, trace network requests, set breakpoints, read execution call stacks, resolve Source Maps, profile runtime performance, and preserve intact diagnostic evidence before and after interactions. From elementary clicks and scrolls to deep breakpoint inspection and bottleneck diagnosis, everything is handled natively within a single Session.

Furthermore, BrowserScope ensures safe multi-plugin coexistence across DSH 0.1.5-rc.2, 0.1.6-alpha.1, 0.1.6-alpha.2, and 0.1.7-rc.1. Each formal Session selects its browser toolset upon first use (BrowserScope or existing third-party browser tools in the current profile). Once chosen, that Session remains permanently locked to that toolset, while other Sessions can choose independently. This prevents contaminated cross-plugin states, detached tabs, and conflicted authentication sessions.

Table of Contents

• Validation Results
• Feature Highlights
• Installation
• Tool Reference
  • Browsing & Interaction
  • Console & Network
  • Breakpoints & Sources
  • Performance & Diagnostics
  • Live View & Manual Takeover
  • Extensions & Environment
  • Session Arbitration
• Technical Specs (TECHNICAL.en.md)
• Validation Report (VALIDATION.en.md)
• 简体中文 (README.md)
• Compatibility
• Feedback & Issues
• License

Validation Results

All tests are conducted under real Chromium, genuine DSH Web environments, and realistic production code bases, avoiding artificial mocks or simplified toy fixtures.

Core Capabilities

• 30 Browser Tools fully passed in real Chromium environments.
• 9 Native Workbench Views verified in live DSH Web workflows.
• Multi-Plugin Coexistence verified through session-scoped selection, locking, runtime release, independent choice, and restart persistence on DSH 0.1.5-rc.2.
• 4 DSH Versions tested across compatibility matrix.
• Sustained Stress Testing (30 min × 3 tiers) with stable performance and leak-free memory profiles.

Verification Matrix

For complete test protocols, raw metrics, and layered breakdown, please see VALIDATION.en.md.

Feature Highlights

Unified Single-Window Diagnostic Loop

Agent conversations, target web pages, tab bars, address inputs, and DevTools inspections reside synchronously in the DSH right sidebar. When anomalies occur, there is no need to alternate between disparate application windows — inspect DOM hierarchies, console logs, network events, and script call stacks in place.

Real Scenario: An unexpected layout glitch occurs. The Agent invokes browser_snapshot to inspect DOM styles, discovering a container whose display was asynchronously toggled to none. It then leverages browser_debugger to place a breakpoint in the offending script, traces the original position via Source Maps, and resolves the async state race condition without manual intervention.

First-Choice Locking: Stable Session Tooling

Before the first browser interaction in a formal Session, the user or model selects either BrowserScope or pre-existing third-party browser tools. Prior to selection, browser tools remain concealed from the Agent to prevent premature invocation.

Selecting BrowserScope locks the Session exclusively to BrowserScope. Selecting third-party tools ensures BrowserScope refrains from registering tools or allocating runtime resources in that Session. Tooling cannot be swapped mid-session; switching plugins simply requires creating a new Session. Other Sessions choose independently without disturbing third-party plugin processes or configs.

Releasing BrowserScope resources safely dismantles its internal pages and debugger connections while preserving the Session's tooling lock. Tool selections automatically persist across DSH restarts and Agent Scope replacements.

Minified Production Code? Restored Instantly

Bundle compressed into a single minified line? Connect the CDP Debugger, resolve Source Maps, and navigate the original source tree directly. Call stacks, variable scopes, and breakpoint targets are mapped back to authoring coordinates.

Real Scenario: A production runtime throws Uncaught TypeError: Cannot read property 'data' of undefined at minified coordinate bundle.min.js:1:47392. The Agent pauses execution via browser_debugger, extracts the Source Map, maps the fault directly to src/api/fetchUser.ts:23:15, and pinpoint missing async exception guards.

Transparent Network Timings & Interception

Network journals are ordered chronologically, with incremental markers clearly illustrating asynchronous request lifecycles. Ideal for catching stale cache overrides, out-of-order responses, and network race conditions.

Dual-Page Split View Monitoring

Inspect two real pages simultaneously with independent screencasts and isolated focus targets. Arrange top-to-bottom for responsive checks or side-by-side for comparative page flows.

Immutable Incident Forensics

Debug sessions encapsulate page identities, action sequences, context topology, and build identifiers into a unified diagnostic bundle.

Take checkpoints before and after interactions; compare states to generate verifiable incident reports.

Performance & Memory Auditing

Investigate CPU spikes, main-thread blocking, and memory leaks. Export traces, capture CPU profiles, and record Heap Snapshots directly to session-isolated artifact storage without exhausting LLM context limits.

Installation

Requires Node.js ^22.19.0 or >=24.0.0, and a functional DSH Web Profile.

1.0.0-rc7 targets DSH 0.1.7-rc.1 and 0.1.7-rc.2 using the same browser business source as the validated RC6. Before installing, verify that the exact version has been published on the npm Registry; otherwise use a local tarball checked against its candidate identity file and SHA-256. Freezing and public release are separate steps and cannot be inferred from the package version alone.

dsh plugin --profile web add dsh-browser-scope@1.0.0-rc7 --ignore-scripts --config.auto-install-peers=false

Or install via local tarball:

dsh plugin --profile web add ./dsh-browser-scope-1.0.0-rc7.tgz --ignore-scripts --config.auto-install-peers=false

Enable in your profile's cordis.patch.yml:

- insert:
    - id: browser-tools
      name: dsh-browser-scope

Launch DSH Web, create a new Session, and send an initial message. Open the "Browser" menu adjacent to the input prompt, select "Use DSH BrowserScope" or "Use other browser tools", and the selection will lock for that Session.

When upgrading from the legacy dsh-browser-tools package, remove the previous package first. Keep id: browser-tools and the $DSH_HOME/browser-tools data directory intact. Avoid co-installing both packages in the same profile.

Tool Reference

Browsing & Interaction

Console & Network

Breakpoints & Sources

Performance & Diagnostics

Live View & Manual Takeover

Extensions & Environment

Session Arbitration

Technical Specs

For complete schema definitions, controller state machines, security invariants, and RPC contracts, see TECHNICAL.en.md.

Validation Report

For comprehensive multi-environment empirical test results, see VALIDATION.en.md.

Compatibility

The target DSH range for 1.0.0-rc7 is 0.1.5-rc.2, 0.1.6-alpha.1, 0.1.6-alpha.2, 0.1.7-rc.1, and 0.1.7-rc.2, with Cordis >=4.0.2 <5 and Schemastery >=3.18.2 <4. RC7 retains RC6's browser business code; check the Registry for the exact npm version before using the install command, and verify candidate freezing and GitHub publication separately.

Candidate identity is anchored by external candidate-identity.json and tarball digest.

Feedback & Issues

For bugs, compatibility issues, or feature requests, please submit an issue on GitHub Issues. Include your DSH version, BrowserScope version, OS, Node.js version, and any co-installed browser plugins.

Security vulnerabilities should be reported privately according to our Security Policy. Never submit credentials, cookies, or raw session logs in public channels.

License

MIT