DeepSeek Harness Plugin

Why-147369/dsh-line-pool#dsh-line-pool

Category Development & Runtime Added 2026-10-17

Outbound route pool for DeepSeek Harness. Ships 15 seed routes plus a 20-entry candidate pool covering 7 target kinds (GitHub raw/codeload/main, npm registry, PyPI index, HuggingFace, general). Routes are verified before use: upstream IP lists go through a TLS handshake with full certificate-chain validation (a bare TCP check can be answered locally and report dead IPs as healthy), and failures advance a cooldown ladder of 2/5/15 minutes with the fastest healthy route picked per target kind. Routes are applied by rewriting the URL with one of four rules (prefix, registry, index, host-replace), reaching git, pip, npm, pnpm, gh, curl and wget through three paths: the shell seam (download commands the model runs through the bash tool are intercepted and rewritten automatically; commands wrapped by the pwsh tool, and fetches made by the host itself or the renderer, are not covered), two registered tools the model can call directly (line_pool_status, line_pool_run), and child-process spawn. Multi-line commands keep their line breaks and only the download segment is touched. URLs carrying credentials (user:token@host) are never rewritten, so tokens are not forwarded to third-party mirrors. No global config is modified. A sidebar panel lists every route with latency, failure reason and cooldown countdown, supports per-route retest and enable/disable, and shows live TUN/proxy status from network-adapter and loopback port checks. The candidate pool is re-verified every 24 hours so newly usable routes are added and dead ones dropped. 570 tests, 87% line coverage.

Install

# from GitHub (first run asks for allowBuilds approval — follow the hint, retry)

dsh plugin --profile web add github:Why-147369/dsh-line-pool#path:/dsh-line-pool

Any plugin you install runs third-party code with your own permissions — it can read your files, use your credentials, and reach the network, and tool approvals don’t sandbox it. GitHub-sourced plugins also run build scripts at install time — pnpm blocks those until you allow them, so an install can stop with ERR_PNPM_GIT_DEP_PREPARE_NOT_ALLOWED or ERR_PNPM_IGNORED_BUILDS; dsh prints the exact key to add under allowBuilds in your profile’s pnpm-workspace.yaml, and the install works on the next run. Allowing a build is a trust decision: only install sources you trust, and pin a commit (github:owner/repo#sha).

Links

More in this category

View the whole category →

Community comments

Comments are public GitHub Discussions. Loading them connects to GitHub and Giscus; a GitHub account is required to post.