deepseek-harness/packages/web
2026-07-29 18:38:56 +08:00
..
tool-web docs(i18n): address automated review 2026-07-29 17:46:06 +08:00
web docs(i18n): address automated review 2026-07-29 17:46:06 +08:00
web-fetch-local docs(i18n): record proofread README pairs 2026-07-29 15:30:44 +08:00
web-search-deepseek docs(i18n): address automated review 2026-07-29 17:46:06 +08:00
web-search-exa docs(i18n): record proofread README pairs 2026-07-29 15:30:44 +08:00
web-search-perplexity docs(i18n): resolve follow-up review findings 2026-07-29 18:38:56 +08:00
AGENTS.md docs(web): codify credentialed redirect policy 2026-07-19 21:56:02 +08:00
README.i18n.yaml docs(i18n): record proofread README pairs 2026-07-29 15:30:44 +08:00
README.md docs: translate remaining READMEs 2026-07-26 05:06:39 +08:00
README.zh.md docs(i18n): proofread README translations 161-180 2026-07-29 15:29:39 +08:00

web/ - web capability family

English | 中文

The web access capability seam: an abstract web interface, search/fetch provider implementations, and the model-facing web tools. All product packages.

Package Role ctx key
web/ Abstract web seam (search/fetch provider registries + selection + vocabulary + WebError) ctx.web
web-search-exa/ Exa-backed WebSearchProvider (registers on ctx.web)
web-search-perplexity/ Perplexity-backed WebSearchProvider (registers on ctx.web)
web-search-deepseek/ DeepSeek-backed WebSearchProvider using native web_search through the Anthropic-compatible API (registers on ctx.web)
web-fetch-local/ Anonymous public HTTP(S) WebFetchProvider (registers on ctx.web)
tool-web/ Model-facing web_search/web_fetch tool schemas (registers on ctx.tools)

The interface lives at web/web/. Unlike bash/fs, the seam spans two capabilities (search and fetch) with potentially multiple providers each: ctx.web is one web-access middle layer with one provider-selection policy, one abort/error vocabulary, and one product-facing "how this harness reaches the web" config surface. Providers register capabilities, not tools; tool-web is the only owner of model-facing names, schemas, prompt guidance, and presentation. A search provider swap does not change how the model asks for a query, and a fetch implementation swap does not change how the model asks for a URL.

See the web capability seam Agent Note for the design rationale, including why search and fetch are deliberately one seam and why web_fetch's SSRF protection is deferred.