Tianyi Cui 26339144e3 fix(docs): address Codex review round 2 — repoint every remaining moved-policy citation 2 月之前
..
tool-web 8ca82d03ab refactor(tool-web): port web tools to the render-intent union 2 月之前
web 7441307251 fix(web): open WebError.code to string, aligning with other seams 2 月之前
web-fetch-local 8395722db5 fix: address codex review findings on web seam 2 月之前
web-search-deepseek 26339144e3 fix(docs): address Codex review round 2 — repoint every remaining moved-policy citation 2 月之前
web-search-exa c3424e5487 fix(docs): address Codex review round 1 on the AGENTS.md rewrite 2 月之前
web-search-perplexity 26339144e3 fix(docs): address Codex review round 2 — repoint every remaining moved-policy citation 2 月之前
README.md cf71c0b215 fix: address web seam review findings 2 月之前

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.