Tianyi Cui 2304f7a245 Merge origin/master: adopt the DeepSeek Harness SDK product name 2 luni în urmă
..
tool-web f256f3961d feat(system-prompt): prompt variables, persona-as-section, tool-guidance ownership 2 luni în urmă
web 1905c809e3 Merge remote-tracking branch 'origin/master' into simpl-c-web-observation 2 luni în urmă
web-fetch-local de79553d4f refactor(web): drop the unconsumed observation surface 2 luni în urmă
web-search-deepseek dca7a436e4 docs: update product name 2 luni în urmă
web-search-exa dca7a436e4 docs: update product name 2 luni în urmă
web-search-perplexity dca7a436e4 docs: update product name 2 luni în urmă
README.md cf71c0b215 fix: address web seam review findings 2 luni în urmă

README.md

web/ - web capability family

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 RFC for the design rationale, including why search and fetch are deliberately one seam and why web_fetch's SSRF protection is deferred.