Skip to content

Web Search Plus v2.9.1

Choose a tag to compare

@robbyczgw-cla robbyczgw-cla released this 10 Jul 12:41
94fcc52

Web Search Plus gives agents one stable search tool and one extraction tool across a provider mesh without locking operators into a single API. v2.9.1 is a focused maintenance release: safer local state, fairer long-page extraction, and cleaner release mechanics.

Highlights

  • Cache operations now respect state ownership. Cache stats and clear operations recognize only complete WSP search-cache envelopes. Provider performance, provider health, usage telemetry, unrelated JSON, and corrupt foreign files in the shared cache directory are preserved instead of being counted, deleted, or crashing cache stats.
  • Parallel long-page extraction is no longer benchmarked through an artificial 6k ceiling. The default full_content budget is now 60k characters per result / 120k total, with parallel.max_chars_per_result and parallel.max_chars_total available for smaller operator-defined payloads. Because the default allowance is up to 10× larger than before, Parallel calls can transfer more content and may use more latency/provider quota. (#86)
  • Release preparation is atomic. scripts/prepare_release.py updates every public version surface together and fails loudly if a surface drifts. (#83)
  • Release metadata and documentation are aligned. The stale v2.9.0 User-Agent was corrected (#82), and Serper extraction is represented consistently across the streamlined README and guides (#84).

Credits

Ecosystem acknowledgement

  • @serpapi — for its continued work across the search API ecosystem.

Verification

The candidate passed 472 tests, Ruff, compile checks, generated documentation drift checks, privacy scanning, fresh-clone verification, and a regression against a copy of a real operator cache containing 1,437 search envelopes and 33 stored web pages. Foreign state, including invalid UTF-8 JSON bytes, remained hash-identical.

Upgrade

hermes plugins update web-search-plus

Restart or reset the Hermes session afterward so the updated plugin code is loaded. No configuration migration is required.