cfanmaoli/kimi-webbridge-dsh

kimi-webbridge-dsh is a native plugin built specifically for DeepSeek Harness (DSH). Its job is to bridge the Moonshot Kimi browser extension into the host so a DSH model session can drive a real local browser through documented, official capabilities. The plugin ships three responsibilities: it provisions the matching platform daemon binary from the official manifest with SHA-256 verification and stores it under ~/.kimi-webbridge/bin/, it bundles and registers the official skill documentation (including its references/ folder) as the kimi-webbridge skill at startup, and it exposes a thin kimi_webbridge tool whose only action is status, reporting daemon, extension, and registered-skill health. Installation is a single dsh plugin --profile web add kimi-webbridge-dsh; the package carries its own bundle patch, so no manual edit of cordis.patch.yml is required and a single DSH restart activates it.

The intended workflow begins with loading the kimi-webbridge skill, triggered by phrases like browser, webpage, or screenshot, and also by requests such as "build a reusable CLI for this site". The user or agent then calls kimi_webbridge.status to confirm that the daemon is reachable and the Chrome extension is connected; the plugin will silently start or even install the daemon if autoStartDaemon and autoInstallDaemon are left at their defaults. Once green, the actual browser control follows the bundled skill documentation: a POST to http://127.0.0.1:10086/command with a JSON body {action, args, session} makes the extension execute the requested action on the user's open browser tab. The plugin is aimed at DSH users who need the model to interact with live web pages, capture screenshots, or expose website actions as reusable commands.

Dependencies and limits are clearly bounded. The plugin only imports @deepseek-ai/* packages from the host as peer dependencies and never bundles copies; it has been verified against DSH 0.2.0-rc.1 and its peer range covers every 0.1.x and 0.2.x release since 0.1.0-rc.7. The browser extension itself is not auto-installed and must be added manually from the Chrome Web Store and connected on the extension side, with status reporting extension_connected: true before use. On Windows, any JSON request body containing non-ASCII characters must be delivered through a temporary file because the shell otherwise mangles the payload, and the skill doc spells this out. License is MIT. Configurable knobs (baseUrl, requestTimeoutMs, autoStartDaemon, autoInstallDaemon, daemonVersion, registerSkill) can be overridden per-id in ~/.dsh/profiles/web/cordis.patch.yml. Note that status.skills being empty is expected, because the upstream daemon only natively recognizes Claude Code, Codex, Hermes, OpenClaw, and Kimi, so this plugin is the sole path by which DSH acquires the skill. Finally, on first run always inspect status and hand any returned command straight back to the user; the plugin must never self-execute upgrade, stop, restart, or uninstall, since those actions would kill an active daemon.