DeepSeek Harness Plugin Hub

发布与管理完整 Harness Profiles,发现适合你的插件。

探索

插件目录环境预设文档中心动态

社区

发布插件联系我们报告问题

相关链接

Plugin Hub GitHubDeepSeek Harness 官方项目系统状态隐私说明
© 2026 DeepSeek Harness Plugin HubPowered byPaxTech

独立、非官方社区项目,与 DeepSeek 官方无隶属、授权或背书关系。

Crw — DeepSeek Harness 插件(DSH Plugin)
← Plugins

dsh-crw

Crw

由 fastCRW 支持的 DeepSeek Harness 网页搜索和获取提供程序(ctx.web)

插件会安装到这里;不确定时保持 web。

npx -y @deepseek-ai/dsh plugin --profile web add dsh-crw@0.1.0
README兼容性版本

兼容性与来源证明

Crw 以 dsh-crw 发布,当前版本为 0.1.0。Plugin Hub 会校验它的 manifest,并保存精确安装来源,便于复现安装结果。

DSH 兼容范围
*
运行环境
any
发布来源
npm
Registry 更新时间
2026/9/20

版本

0.1.0stable
2026/8/14

相关插件

正在加载相关插件…

最新版
0.1.0
DSH
*
HMR
重启进程
Tree shaking
未声明可安全裁剪
解包体积
36.7 kB
文件数
12
Surface
any
许可证
MIT
发布源
npm
GitHub
★ 3
周下载
87
最近提交
2026/8/14
查看源码 ↗
项目主页 ↗
README Badge

点击下方 Badge 复制 Markdown,粘贴到 README 即可。

这是你的 Plugin?认领权益 · 优先安全扫描

验证 package.json 声明的 GitHub 仓库,即可管理这个公开页面。认领后,Hub 会优先安排当前版本的安全扫描,并在通过后公开展示结果。

认领这个 Plugin →
报告问题
DeepSeek Harness Plugin Hub
ProfilesPlugins分类动态文档登录管理 Profiles
ProfilesPlugins分类动态文档登录

相关插件

继续浏览 search-research 分类下经过校验的插件。

Browser Skill Dsh Plugin@wxg-prc-cpg/browser-skill-dsh-plugin向模型提供 BrowserSkill 浏览器自动化(browser_* 工具)的 DeepSeek Harness 工具插件Weknora@wxg-prc-cpg/dsh-weknora适用于 DeepSeek Harness (dsh) 的 WeKnora 知识检索工具:通过自有知识库进行语义搜索、文档阅读以及 RAG/代理回答。Free Searchdsh-free-searchDeepSeek Harness 的免费网页搜索:13 个引擎(Bing/DuckDuckGo/AnySearch/SearXNG/Exa/Tavily/Keenable/Firecrawl 无需密钥;Parallel/Perplexity/SerpBase/DeepSeek 需要密钥),支持时间筛选、平台搜索和 web_fetch,并提供网页设置界面。Find Plugindsh-find-plugin在代理中查找 DeepSeek Harness 插件——实时搜索 GitHub 上的 dsh-plugin 主题,并按星标数排序。

README

dsh-crw

fastCRW-backed web_search and web_fetch for DeepSeek Harness.

The harness treats web access as a capability seam (ctx.web) with pluggable providers. This package registers two of them under the id crw, so the model keeps the exact same web_search / web_fetch tools and only the backend changes.

Why

The base composition ships web_search on, and web_fetch off. Its own config says why:

Fetch stays disabled and no fetch provider is mounted: that provider defers SSRF protection and the model would choose the request target.

That is a fair call. The in-box HTTP fetch provider runs fetch() in the harness process, and its README names the gap outright: no blocking of private, loopback, link-local or multicast destinations, no DNS-resolve-then-validate. A model that picks http://169.254.169.254/ gets your cloud metadata endpoint.

fastCRW resolves and validates the target server-side and refuses private ranges, so the harness process never opens a connection the model chose. That is what makes turning fetch on reasonable, and it is why fetch: true lives in this bundle rather than upstream.

The second reason is that plain HTTP is not how the open web reads any more:

URLin-box HTTP providerdsh-crw
producthunt.com403, a Cloudflare interstitial200, 27,559 chars of markdown
zillow.com403, "Access to this page has been denied"200, real page content
news.ycombinator.com200, raw HTML for the tool to convert200, markdown from the source

fastCRW escalates per page from plain HTTP through its browser tiers only when a page needs one, so the common case stays fast and the hard case still answers. Not every wall falls: an interactive Cloudflare challenge still wins sometimes.

Install

export CRW_API_KEY=...          # fastcrw.com, 500 free credits, no card
dsh plugin --profile default add dsh-crw
dsh --profile default

Get a key at fastcrw.com. The free tier is a one-time 500 credits and needs no card; one page is one credit.

To install straight from this repo instead, pin a commit and allow the build. A git install fetches sources, so pnpm has to run this package's prepare script to produce lib/, and pnpm 10+ requires you to say so explicitly:

# $DSH_HOME/profiles/<name>/pnpm-workspace.yaml
allowBuilds:
  dsh-crw: true
dsh plugin --profile default add github:us/dsh-crw#<sha>

That allowance runs this package's build on your machine at install time, so pin the commit rather than tracking the branch.

Verify the layer before booting:

dsh --profile default --dump-config    # shows a "# == dsh-crw" layer

What the bundle does

The shipped cordis.patch.yml applies three changes over @deepseek-ai/dsh-base:

  • points web.searchProvider and web.fetchProvider at crw
  • turns on tool-web's fetch and raises both timeouts, since a page behind a JS or anti-bot wall escalates through browser tiers before it answers
  • mounts this plugin, reading $CRW_API_KEY

The base layer's own DeepSeek search provider stays mounted, so switching search back is one line in your profile's cordis.patch.yml:

- id: web
  config:
    searchProvider: deepseek-official
    fetchProvider: crw

Config

KeyDefaultMeaning
apiKey$CRW_API_KEYfastCRW API key. Required against the cloud endpoint; empty is fine when self-hosting.
baseURLhttps://fastcrw.com/apiEndpoint base; /v1/search and /v1/scrape are appended.
searchtrueRegister the search provider.
fetchtrueRegister the fetch provider.
answerfalseAsk fastCRW to synthesize an answer over the results, returned as the seam's content. Adds an LLM call per search.
maxBodyChars100000Cap on returned page characters, matching the in-box provider.
- id: crw
  name: dsh-crw
  config:
    apiKey: !!js process.env.CRW_API_KEY
    answer: false

Self-hosting

fastCRW is AGPL-3.0 and the engine is one binary, so the whole web layer can stay on your own machine:

crw serve
- id: crw
  name: dsh-crw
  config:
    baseURL: http://127.0.0.1:3002

A self-hosted endpoint takes no credential, so apiKey may be empty. The provider only insists on a key when it is pointed at the cloud endpoint.

Mapping notes

  • Search. POST /v1/search. Each result maps to a WebSearchSource: url, title, and snippet from the result's snippet or, failing that, its description. A result without a URL is dropped rather than given an invented one. With answer on, the synthesized answer becomes the seam's content. The seam owns the final maxResults truncation.
  • Fetch. POST /v1/scrape with formats: ['markdown']. The body kind is text, not html: fastCRW already returns markdown, and html would send it back through the tool's turndown pass to convert converted output.
  • Non-2xx targets. fastCRW reports a 404 target as success: false while still returning what it got. The seam's contract is the other way round, so an envelope carrying a status code is always a result. A WebError is reserved for failing to retrieve the resource at all: a rejected URL, a bad key, an exhausted balance.
  • No renderer hint is sent. fastCRW's escalation ladder decides per page whether plain HTTP is enough.

Development

bun install
bun test
bun run build

License

MIT.