Turtleandturtle1999
2f01ad549c
The HTTP fetch provider resolved each hostname, rejected any non-public answer, and pinned the connection. That refused every page behind TUN-mode proxies with fake-IP DNS and did not confine a model that has shell network access. Requests now go through the installed proxy dispatcher and the system resolver with no address restriction. HttpFetchResolver and the HttpFetchProvider resolver parameter are removed; the upgrade guide covers the migration. Co-authored-by: turtle1999 <301751225+turtle1999@users.noreply.github.com>
2.6 KiB
description, kind
| description | kind |
|---|---|
| Package map for the web access capability family: the search/fetch service, its provider backends, and the model-facing tools that consume them. | package-group |
web/ — web access capability family
English | 中文
Summary
The web/ packages let models search the public web and fetch HTTP(S) pages through the web_search and web_fetch tools. Deployments can choose Exa, Perplexity, or DeepSeek for search and anonymous HTTP(S) or DeepSeek for fetch; availability and resource limits depend on the configured provider. Use this family for search and page retrieval, not interactive browsing, content extraction, or per-URL policy enforcement. Models receive consistent tool behavior, cancellation, and error reporting when providers change.
Table of Contents
Packages
Six packages play the web roles; the subsystem reference owns the exhaustive vocabulary and contracts.
| Package | Role | ctx key |
|---|---|---|
web/ |
Search/fetch service: search and fetch URLs through interchangeable backends, one selection and error policy | ctx.web |
web-search-exa/ |
Searches the web through Exa | registers on ctx.web |
web-search-perplexity/ |
Searches the web through Perplexity | registers on ctx.web |
web-search-deepseek/ |
Searches through DeepSeek Messages | registers on ctx.web |
web-deepseek-api/ |
Searches and fetches pages through the DeepSeek Search and Fetch APIs | registers on ctx.web |
web-fetch-http/ |
Fetches HTTP(S) pages anonymously | registers on ctx.web |
tool-web/ |
Exposes web_search and web_fetch to the model |
registers on ctx.tools |
Related documentation
Start with the subsystem reference for the shared vocabulary, then the design decision behind the single provider-selection service.
- Web subsystem — the search/fetch requests and results, provider availability,
WebError, and the fetch network policy. - Web capability seam decision — why search and fetch share one provider-selection service.
Dev Note
Working context for maintainers — click to expand
None.