titanwings/dsh-better-browser
DSH real browser plug-in: allows the Agent to operate the user's logged-in browser through Kimi WebBridge and provides 13 webbridge_* tools
dsh-better-browser lets a DSH agent use your already-logged-in real browser — the exact Chrome, Edge, or Brave instance you have open with your accounts, cookies, and local state intact. Instead of launching a fresh headless browser (which has no cookies or saved logins), it connects to your running browser via the Chrome DevTools Protocol (CDP) remote debugging port. This means the agent can access sites where you are already signed in without needing credentials, can see your current browsing state, and can interact with pages as you would. Features: connect to an existing browser session (no new context, no login needed for authenticated sites); navigate, click, fill forms, take screenshots, read page content; existing tabs controlled or new tabs opened; no JavaScript injection into pages; Kimi WebBridge integration available for Kimi-specific workflows. Compared to headless browser plugins, dsh-better-browser is the practical choice when the target site requires real-user cookies (banking, SSO, corporate intranet) or when you want to hand off a mid-session browser state to the agent.
Install
dsh plugin --profile web add github:titanwings/dsh-better-browser#v0.3.6Install by pinning the latest release tag: dsh plugin --profile web add github:titanwings/dsh-better-browser#v0.3.6. Or install from a Kimi-hosted script: curl -fsSL https://cdn.kimi.com/webbridge/install.sh | bash (installs the Kimi WebBridge integration). Requires Node.js >= 22.19 and a running Chromium-family browser with remote debugging enabled (launch Chrome/Edge/Brave with --remote-debugging-port=9222). The agent connects to the existing browser session — it uses your already-logged-in cookies and local state. Remove with dsh plugin --profile web remove dsh-better-browser (for the Kimi variant: dsh plugin --profile web remove @dsh-external/dsh-kimi-browser).
Compatibility
DeepSeek Harness web profile. Node.js >= 22.19. Requires a Chromium-family browser (Chrome, Edge, Brave) running with --remote-debugging-port=9222. Connects to the existing browser session via Chrome DevTools Protocol (CDP): uses existing cookies, local storage, and login state — no new browser context, no login required for sites you are already signed in to. The agent can control existing tabs (navigate, click, fill, screenshot) and open new tabs. Does not inject JavaScript into pages. Separate Kimi WebBridge variant available via Kimi-hosted install script.
Details
- Repo: titanwings/dsh-better-browser
- Category: Agent Capabilities
- Stars: 10
- Version: v0.3.6 GitHub source install from titanwings/dsh-better-browser (no npm package; 2026-08-23)
- Last push: 2026-08-13
- First seen: 2026-08-13
Recent updates
The current README documents: why use your real browser (existing login state, cookies, local storage vs. headless's fresh context), CDP remote debugging port requirement (--remote-debugging-port=9222), Node.js 22.19+ requirement, install paths (GitHub pinned tag v0.3.6, Kimi WebBridge via curl script), the Kimi variant uninstall command, key agent capabilities (navigate/click/fill/screenshot/tab management), and the no-JS-injection guarantee.
FAQ
- Does it launch a new browser?
- No — it connects to your already-running Chrome, Edge, or Brave instance via the CDP remote debugging port. Your existing cookies, logins, and local storage are all available to the agent.
- How do I enable remote debugging?
- Launch Chrome/Edge/Brave with --remote-debugging-port=9222 added to the command-line arguments. On macOS: open -a 'Google Chrome' --args --remote-debugging-port=9222.
- Can the agent inject JavaScript into pages?
- No — dsh-better-browser deliberately does not inject JavaScript into pages; it operates through CDP's higher-level browser control primitives.
Alternatives
Clizo1209/dsh-playwright-browser · cyijun/dsh-surfing-plugin · omdsh-dev/dsh_workflow