bpc-oss/chrome-faithful#dsh-plugin-chrome-faithful

English · 简体中文

First-party DeepSeek Harness (DSH) bundle for Chrome Faithful. It mounts the existing Chrome Faithful MCP server through DSH's official MCP client, retaining all exact-profile routing, authentication, redaction, and browser-control behavior without duplicating the 38 tools as native Cordis implementations.

Compatibility

• DSH: @deepseek-ai/dsh 0.1.0-rc.6 or the same reviewed RC contract
• Node.js: >=22.12.0
• Chrome Faithful core: exactly 0.4.0, the same version as this bundle

DSH is currently an RC. Revalidate this bundle when moving to a newer DSH RC; the host owns @deepseek-ai/dsh-mcp-client, so this package deliberately does not install another copy.

Install

After both packages are publicly available, add the bundle to the target DSH profile:

dsh plugin --profile web add @bpc-oss/dsh-plugin-chrome-faithful@0.4.0

Chrome Faithful core must be published first because the bundle pins the exact core version. For private acceptance, pack both packages and install both local tarballs into a disposable DSH profile; do not publish or mutate a live profile merely to validate source changes.

Configure

Create the private Chrome Faithful configuration outside the source tree as described in the root project README. The existing compatibility path is:

%LOCALAPPDATA%\AgentOS\agentos-chrome-cdp\config.json

Set AGENTOS_CHROME_CONFIG only when using a different absolute path. The bundle passes that variable explicitly when present and embeds no secret.

For text-only DeepSeek models, chrome_visual_extract returns local OCR text, confidence, and normalized screenshot coordinates as text JSON. The default adapter requires a user-installed PaddleOCR runtime and explicit local PP-OCRv5 mobile model directories:

CHROME_FAITHFUL_PYTHON=C:\Python311\python.exe
CHROME_FAITHFUL_PPOCR_DET_MODEL_DIR=C:\Models\PP-OCRv5_mobile_det
CHROME_FAITHFUL_PPOCR_REC_MODEL_DIR=C:\Models\PP-OCRv5_mobile_rec

Live quality acceptance passed on the direct production MCP path from the extension through the bridge and MCP server to chrome_visual_extract: 7/7 blocks were detected with 99.43% raw and 100% non-whitespace character accuracy. DSH model consumption of chrome_visual_extract output was not evaluated. The optional VLM remained disabled, uninstalled, unevaluated, and not approved.

The optional CHROME_FAITHFUL_OCR_BACKEND and CHROME_FAITHFUL_VLM_BACKEND variables accept a shell-free JSON-array CLI specification such as cli:["executable","arg"] or an exact loopback HTTP URL with an explicit port. The VLM path is disabled when unset. Chrome Faithful does not install Python packages or models, download weights, accept remote backend URLs, follow redirects, or fall back to a cloud service.

The bundle forwards only these six defined string values: AGENTOS_CHROME_CONFIG, CHROME_FAITHFUL_OCR_BACKEND, CHROME_FAITHFUL_PYTHON, CHROME_FAITHFUL_PPOCR_DET_MODEL_DIR, CHROME_FAITHFUL_PPOCR_REC_MODEL_DIR, and CHROME_FAITHFUL_VLM_BACKEND.

On activation, DSH exposes namespaced tools such as:

mcp__chrome_faithful__chrome_profiles
mcp__chrome_faithful__chrome_selftest
mcp__chrome_faithful__chrome_cdp

Initial MCP startup is fail-loud. Missing configuration, unresolved packages, or duplicate MCP namespaces do not silently produce an active bundle with no tools.

Security boundary

This integration controls real, logged-in Chrome profiles. Tool results are visible to the model and host configured in DSH. chrome_cdp with action=send is unrestricted raw CDP and can read authenticated page content, cookies, browser storage, tokens, URLs, and headers. Install this bundle only in a fully trusted DSH profile and do not expose it to untrusted models, users, plugins, or remote hosts.

The extension-to-bridge connection stays on authenticated localhost. Review the project's security model before enabling the integration.

Verification status

Repository tests cover bundle composition, conditional environment evaluation, package isolation, absolute launcher resolution, and startup failure behavior. A disposable-profile DSH startup and baseline tool-call acceptance passed for the pre-visual 37-tool surface. The later direct MCP quality acceptance covered the 38th tool, chrome_visual_extract, but did not evaluate a DSH model consuming that result. Revalidate both boundaries for every newer DSH RC.