dsh.so
EN
English中文
@lyd123qw2008/pi-control-chrome avatar

@lyd123qw2008/pi-control-chrome

Chrome and Edge browser control for Pi, Codex and DSH. Drives your real browser profile, login state and tabs through an MV3 extension and a local loopback Bridge - native CDP, AX-first semantics, no separate browser.

Ecosystem pluginBrowserWeb search
Verification
L5 · Ecosystem plugin
Ecosystem plugin
Risk
Critical
Health
Stable
Trust
Silver

Install verification: Ecosystem plugin: installs via dsh plugin add but declares no dsh.bundle and mounts no plugin capability — the L1-L5 install ladder does not rate it; the security scan still runs.Install verification details →

What it doesAI

Lets Pi, Codex and DSH agents drive your real Chrome/Edge profile, logins and tabs via an MV3 extension and local loopback bridge.

  • Controls your real browser profile, login state and tabs
  • MV3 Chrome/Edge extension plus local loopback Bridge
  • Native CDP with AX-first semantics, no separate browser
browserAIweb-searchAI

Capability tags are AI-inferred or rule-extracted from the README (see badge) — vocabulary-limited, not install-verified. AI = inferred; README = literal keyword from the readme.

Installation

dsh plugin --profile web add pi-control-chrome
verified 0.8.0

Install method: npm · runtime test inconclusive (L5 unknown)

Verification & Compatibility○ Ecosystem plugin

Grouped by plugin version: each card lists the dsh versions actually tested against that artifact version and their install verdicts (L5 wins). Untested combinations are omitted — absence means untested, never assumed compatible. L1–L3 are a plugin-level static archive (independent of the dsh version — the same verdict on every dsh row): they sit in each row's level grid next to L4/L5, marked "static", while their evidence is stored once per plugin inside that row's "checks & evidence" instead of being duplicated per version.

External credentials (plugin-level): none detected

Declared DSH compatibilityfrom package.json · peerDependencies
author declared no dsh version requirement

○ The author declares no dsh version requirement — install is not blocked by version.

Install compatibility matrix (rows = plugin versions〔latest 5〕, columns = dsh versions〔latest 5〕)
○ Ecosystem plugin
At-a-glance → evidence in the cards below
plugin ＼ dshdsh 0.2.1-rc.2
current
dsh 0.2.1-alpha.4dsh 0.2.1-alpha.2
0.8.0○○○
v0.8.0···
Install compatibility (by plugin version, dsh versions within)
Legend:✓ L5 runtime verified○ ecosystem plugin◼ ecosystem app✗ failed
0.8.0npm○ 3 ecosystem plugin2026-10-19

pi-control-chrome

○dsh 0.2.1-rc.2current2026-10-19Ecosystem plugin
Environment & artifact
  • • Node.js: v24.14.0
  • • DSH: 0.2.1-rc.2
  • • Plugin artifact: npm · pi-control-chrome@0.8.0
Levels (L1–L3 plugin-level static archive · L4/L5 newest real verdicts for this combination)
L1 static
Passed
L2 static
Passed
L3 static
Passed
L4 sandbox
Passed
L5 runtime
Unknown
Ecosystem plugin: no install verdict — not a usable dsh plugin (shown as L5 · ecosystem plugin)
Ecosystem plugin

ID: pi-control-chrome@0.8.0@dsh0.2.1-rc.2 · profile: l4-sandbox

Issued: 2026-10-19 · expires: 2026-10-26

View checks & evidence
L1 · Found✓ Passed
Defaulted from L3✓ Passed
defaulted to passed — L3 install spec passed (full-registry L3 sweep policy)
L2 · Structured✓ Passed
Defaulted from L3✓ Passed
defaulted to passed — L3 install spec passed (full-registry L3 sweep policy)
L3 · Install spec✓ Passed
Install command parsed✓ Passed
Source: registry verification · Method: install spec parse · Captured 2026-10-18
DSH version declared✓ Passed
Source: registry verification · Method: DSH version declaration · Captured 2026-10-18
L4 · Install tested✓ Passed
Install executed in confined sandbox✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-19
spec pi-control-chrome · channel npm package · outcome ran · exit 0
check took: 2.9s
Install succeeded✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-19
spec pi-control-chrome · channel npm package · outcome ran · exit 0
check took: 2.9s
Installed artifact confirmed✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-19
spec pi-control-chrome · channel npm package · outcome ran · exit 0
check took: 2.9s
L5 · Run tested? Unknown

not present in web-profile loader inventory

Sandbox install passed✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-19
spec pi-control-chrome · install mode reused L4 scratch
check took: 29ms
Web boot ready✓ Passed
Source: DSH runtime · Method: web boot · Captured 2026-10-19
ready line dsh web: http://127.0.0.1:58032/?token=…
HTTP endpoint served✓ Passed
Source: DSH runtime · Method: HTTP request · Captured 2026-10-19
path / · HTTP 200 · took 29ms
Plugin active in inventory? Unknown
Source: DSH runtime · Method: plugin inventory query · Captured 2026-10-19
verdict not-found · entries 149
phases: active 121 · null 28
not present in web-profile loader inventory

L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.

○dsh 0.2.1-alpha.42026-10-17Ecosystem plugin
Environment & artifact
  • • Node.js: v24.14.0
  • • DSH: 0.2.1-alpha.4
  • • Plugin artifact: npm · pi-control-chrome@0.8.0
Levels (L1–L3 plugin-level static archive · L4/L5 newest real verdicts for this combination)
L1 static
Passed
L2 static
Passed
L3 static
Passed
L4 sandbox
Passed
L5 runtime
Unknown
Ecosystem plugin: no install verdict — not a usable dsh plugin (shown as L5 · ecosystem plugin)
Ecosystem plugin

ID: pi-control-chrome@0.8.0@dsh0.2.1-alpha.4 · profile: l4-sandbox

Issued: 2026-10-17 · expires: 2026-10-24

View checks & evidence
L1 · Found✓ Passed
Defaulted from L3✓ Passed
defaulted to passed — L3 install spec passed (full-registry L3 sweep policy)
L2 · Structured✓ Passed
Defaulted from L3✓ Passed
defaulted to passed — L3 install spec passed (full-registry L3 sweep policy)
L3 · Install spec✓ Passed
Install command parsed✓ Passed
Source: registry verification · Method: install spec parse · Captured 2026-10-18
DSH version declared✓ Passed
Source: registry verification · Method: DSH version declaration · Captured 2026-10-18
L4 · Install tested✓ Passed
Install executed in confined sandbox✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-17
spec pi-control-chrome · channel npm package · outcome ran · exit 0
check took: 6.8s
Install succeeded✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-17
spec pi-control-chrome · channel npm package · outcome ran · exit 0
check took: 6.8s
Installed artifact confirmed✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-17
spec pi-control-chrome · channel npm package · outcome ran · exit 0
check took: 6.8s
L5 · Run tested? Unknown

not present in web-profile loader inventory

Sandbox install passed✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-17
spec pi-control-chrome · install mode reused L4 scratch
check took: 315ms
Web boot ready✓ Passed
Source: DSH runtime · Method: web boot · Captured 2026-10-17
ready line dsh web: http://127.0.0.1:56349/?token=…
HTTP endpoint served✓ Passed
Source: DSH runtime · Method: HTTP request · Captured 2026-10-17
path / · HTTP 200 · took 315ms
Plugin active in inventory? Unknown
Source: DSH runtime · Method: plugin inventory query · Captured 2026-10-17
verdict not-found · entries 149
phases: active 121 · null 28
not present in web-profile loader inventory

L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.

○dsh 0.2.1-alpha.22026-10-15Ecosystem plugin
Environment & artifact
  • • Node.js: v24.14.0
  • • DSH: 0.2.1-alpha.2
  • • Plugin artifact: npm · pi-control-chrome@0.8.0
Levels (L1–L3 plugin-level static archive · L4/L5 newest real verdicts for this combination)
L1 static
Passed
L2 static
Passed
L3 static
Passed
L4 sandbox
Passed
L5 runtime
Unknown
Ecosystem plugin: no install verdict — not a usable dsh plugin (shown as L5 · ecosystem plugin)
Ecosystem plugin

ID: pi-control-chrome@0.8.0@dsh0.2.1-alpha.2 · profile: l3-fullscan

Issued: 2026-10-15 · expires: 2026-10-22

View checks & evidence
L1 · Found✓ Passed
Defaulted from L3✓ Passed
defaulted to passed — L3 install spec passed (full-registry L3 sweep policy)
L2 · Structured✓ Passed
Defaulted from L3✓ Passed
defaulted to passed — L3 install spec passed (full-registry L3 sweep policy)
L3 · Install spec✓ Passed
Install command parsed✓ Passed
Source: registry verification · Method: install spec parse · Captured 2026-10-18
DSH version declared✓ Passed
Source: registry verification · Method: DSH version declaration · Captured 2026-10-18
L4 · Install tested✓ Passed
Install executed in confined sandbox✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-14
spec pi-control-chrome · channel npm package · outcome ran · exit 0
check took: 3.6s
Install succeeded✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-14
spec pi-control-chrome · channel npm package · outcome ran · exit 0
check took: 3.6s
Installed artifact confirmed✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-14
spec pi-control-chrome · channel npm package · outcome ran · exit 0
check took: 3.6s
L5 · Run tested? Unknown

not present in web-profile loader inventory

Sandbox install passed✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-14
spec pi-control-chrome · install mode reused L4 scratch
check took: 80ms
Web boot ready✓ Passed
Source: DSH runtime · Method: web boot · Captured 2026-10-14
ready line dsh web: http://127.0.0.1:60828/?token=…
HTTP endpoint served✓ Passed
Source: DSH runtime · Method: HTTP request · Captured 2026-10-14
path / · HTTP 200 · took 80ms
Plugin active in inventory? Unknown
Source: DSH runtime · Method: plugin inventory query · Captured 2026-10-14
verdict not-found · entries 149
phases: active 121 · null 28
not present in web-profile loader inventory

L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.

v0.8.0github2026-10-14

https://github.com/lyd123qw2008/pi-control-chrome

Ecosystem plugin: installs via dsh plugin add but declares no dsh.bundle and mounts no plugin capability — its level reads L5 · Ecosystem plugin.

Author badges

Embed the official badges in your README to showcase security & install-test status:

dsh.so risk
`[![dsh.so risk](https://www.dsh.so/badge/pi-control-chrome.svg)](https://www.dsh.so/artifact/pi-control-chrome/)`

Security Report

Two automated layers, neither a manual review: a static scan (per-plugin rule checks) and a model-driven dynamic security audit that covers only the subset static-flagged at warn or above and never executes plugin code.

pi-control-chromeAutomated review · daily

Static low, dynamic high — stricter wins → overall high.

static low→dynamic high→overall high
0 critical·0 high
highoverall · high
1static scan · vet primaryvet AST static analysis (npm artifact or git source)
Version binding
plugin versionv0.8.0
scanned version0.8.0npm2026-10-21
current version0.8.0same version
vet verdictclean · npm

Vet is an AST static scan (npm artifact or git source).

show static findings (5)
  • warningnetIp · networkbridge/server.mjs:1341

    const requestUrl = new URL(req.url || "/", `http://127.0.0.1:${port}`);

  • warningnetIp · networkbridge/server.mjs:1372

    const requestUrl = new URL(request.url || "/ws", `http://127.0.0.1:${port}`);

  • warningchildProcess · code-execmcp/mcp-server.mjs:556

    const child = spawn(process.execPath, [

  • warningchildProcess · code-execpi-extension/index.ts:373

    const child = spawn(process.execPath, [

  • warningnetIp · networkskills/pi-control-chrome/scripts/browser.mjs:50

    node browser.mjs view http://127.0.0.1:3000/ --session example-session --turn 1 --screenshot C:\\Temp\\page.png

2dynamic auditmodel reads redacted source context · never executes plugin code
highest gradehigh
merged intooverall high
audited at2026-10-19
findings0 critical·3 high1 medium / 0 low hidden
show 4 audit findings
  • highUnauthenticated /pair endpoint discloses Bridge bearer token to any extension or local processbridge/server.mjs:946

    The token is the only WebSocket authentication. extensionCorsHeaders reflects any chrome-extension://[a-p]{32} origin, and local processes can omit Origin. A malicious extension or local user can obtain the token and open /ws as role=pi, then issue browser evaluate, CDP, upload, and download commands.

  • highbrowser_upload sends arbitrary local file paths to page file inputs without confirmationmcp/mcp-server.mjs:300

    The tool accepts any string or array of local paths and forwards it to the CDP upload path. Untrusted page content can prompt-inject the agent to upload ~/.ssh/id_rsa or credentials to an attacker-controlled file input and submit it; no path allow-list or explicit user confirmation is present.

  • highbrowser_cdp and browser_evaluate expose unrestricted CDP and page JavaScript to model-driven page contentmcp/mcp-server.mjs:328

    Any CDP method is accepted. A malicious page can prompt-inject the agent to call Network.getAllCookies, then Runtime.evaluate or fetch to send session cookies to an attacker. No method allow-list or explicit confirmation gates evaluate/CDP.

  • mediumbrowser_screenshot writes to any resolved path without overwrite confirmationmcp/mcp-server.mjs:560

    The path argument is model/user controlled and is not restricted to a downloads directory. A prompt-injected call can overwrite user-writable configuration or scripts with attacker-influenced screenshot bytes, causing data corruption or denial of service.

High-risk issues found: /pair leaks the Bridge token to any extension/local process, browser_upload can exfiltrate arbitrary local files, and unrestricted CDP/evaluate can steal session cookies; screenshot path write adds medium risk.

Rule: the dynamic audit can only raise risk, never lower it (raise-only, never an exemption); a wrong raise is withdrawn by human review and the tier falls back to the static verdict. Overall verdict = the stricter of the two layers.

Disclaimer: the static scan and the dynamic security audit are both automated analysis, not a security guarantee. Always review what you install.

Activity

Last commit 2026-09-18 · activity: Stable

• Repo created: 2026-08-17

• Stars: ★ 5 · Forks: 2

• Health: Stable — committed within 90 days

Source

GitHub: github.com/lyd123qw2008/pi-control-chrome

Was this page helpful?