Release 2.2.0

Author: github-actions[bot]

…ed/capability-scoped-provider-options.md …es/capability-scoped-provider-options.mdchangelog/unreleased/capability-scoped-provider-options.md renamed to changelog/releases/v2.2.0/entries/capability-scoped-provider-options.md changelog/unreleased/capability-scoped-provider-options.md renamed to changelog/releases/v2.2.0/entries/capability-scoped-provider-options.md

@@ -0,0 +1,8 @@
+created: 2026-04-03
+title: Pi Web Providers v2.2.0
+intro: >-
+  Managed tools now advertise explicit provider-specific option schemas, and provider
+  options are scoped strictly to their respective capabilities.
+source:
+  mode: sync-stable-queue
+  previous_stable: v2.1.0

…ptions-with-explicit-provider-schemas.md …ptions-with-explicit-provider-schemas.mdchangelog/unreleased/structured-tool-options-with-explicit-provider-schemas.md renamed to changelog/releases/v2.2.0/entries/structured-tool-options-with-explicit-provider-schemas.md changelog/unreleased/structured-tool-options-with-explicit-provider-schemas.md renamed to changelog/releases/v2.2.0/entries/structured-tool-options-with-explicit-provider-schemas.md

@@ -0,0 +1,21 @@
+Managed tools now advertise explicit provider-specific option schemas, and provider options are scoped strictly to their respective capabilities.
+
+## 🚀 Features
+
+### Structured tool options with explicit provider schemas
+
+Each managed tool (`web_search`, `web_contents`, `web_answer`, `web_research`) now advertises the exact provider-specific options available for the configured provider directly in the tool schema. This means the agent can discover supported knobs—such as Tavily's `searchDepth` and `country`, Exa's `category` and `userLocation`, or Gemini's `model` and `generation_config`—without relying on documentation or guesswork.
+
+In practice, the agent is more likely to take advantage of provider features like domain filtering, search depth, or location hints when they would improve the quality of results for your query.
+
+*By @mavam and @codex.*
+
+## 🐞 Bug fixes
+
+### Scope provider options by capability
+
+Provider options are now scoped strictly to the managed tool that uses them. This fixes cases where search-only defaults or schema fields could appear to bleed into other tools, such as Exa `web_search` options showing up alongside `web_contents`.
+
+As part of this cleanup, providers with capability-specific defaults now store them under capability-specific configuration blocks, and tools without per-call provider options no longer expose an empty `options.provider` object.
+
+*By @mavam and @codex.*

changelog/releases/v2.2.0/manifest.yaml

@@ -1,6 +1,6 @@
 {
   "name": "pi-web-providers",
-  "version": "2.1.0",
+  "version": "2.2.0",
   "description": "Configurable web access extension for pi with per-tool provider routing and explicit provider option schemas for search, contents, answers, and research.",
   "type": "module",
   "files": [