Master's step-scoped conditional activation resolves each tool's condition before a model step assembles, and both the declarations and dispatch read that admitted set. Prompt assembly no longer carries tool declarations, so tool-web's system-prompt/assemble listener could not remove web_search any more, and removing a declaration there never stopped a repeated call from running. tool-web now registers web_search with a when condition that asks ctx.web.searchReady() about the route of the step's model selection, and its guidance section renders from the step's admitted set. A step that does not admit the tool leaves it out of declarations, guidance, and PTC program bindings, and refuses a call to it as UNKNOWN_TOOL without reaching a provider. Tests that execute web_search directly now run inside a resolved step, as the executor requires for conditional registrations. Docs, the readiness Agent Note, and the event producer/consumer table follow the new mechanism; the tools README gains an explicit conditional-tools anchor for cross-locale links.
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.