robbyczgw-cla/web-search-plus-mcp

v0.5.1 Breaking

This release includes 3 breaking changes for platform teams planning a safe upgrade.

Published 20d MCP Search & Web

View tool

✓ No known CVEs patched

Read the diff → Tool health → What is this tool? →

✓ No known CVEs patched in this version

Affected surfaces

auth

ReleasePort's take

Light signal

editorial:auto 13d

Release v0.5.1 separates Perplexity provider from kilo-perplexity, requiring distinct API keys and config changes; kilo_perplexity is renamed to kilo-perplexity without aliasing.

Why it matters: Update provider configurations before the next deployment cycle to avoid authentication failures due to the split and rename.

Summary

AI summary

Split native Perplexity handling from Kilo gateway routing requiring explicit provider config changes.

Changes in this release

Type	Severity	Summary	CVE
Breaking	Medium	Perplexity provider separated from kilo-perplexity with distinct API keys Perplexity provider separated from kilo-perplexity with distinct API keys Source: llm_adapter@2026-05-21 Confidence: high	—
Breaking	Medium	kilo_perplexity renamed to kilo-perplexity without aliasing kilo_perplexity renamed to kilo-perplexity without aliasing Source: llm_adapter@2026-05-21 Confidence: high	—
Feature	Medium	Web Search Plus logo assets added for documentation Web Search Plus logo assets added for documentation Source: llm_adapter@2026-05-21 Confidence: low	—

Full changelog

Fixed

Split native perplexity from kilo-perplexity so direct Perplexity uses PERPLEXITY_API_KEY, https://api.perplexity.ai/chat/completions, and sonar-pro.
Keep Kilo gateway routing under the distinct kilo-perplexity provider using KILOCODE_API_KEY, https://api.kilo.ai/api/gateway/chat/completions, and perplexity/sonar-pro.
Normalize kilo_perplexity to kilo-perplexity without aliasing it to native perplexity.

Migration

Existing Kilo gateway users who previously selected perplexity with only KILOCODE_API_KEY should switch explicit provider config to kilo-perplexity or set a native PERPLEXITY_API_KEY.

Docs

Add Web Search Plus logo assets used by the README and directory listings.

Tests

Add regression coverage for provider defaults, env-key lookup, missing-key errors, aliases, auto-routing preference, cache separation, and MCP server metadata.
Verified with pytest, compileall, json.tool, git diff --check, ruff, uv build, twine check, privacy scan, and Andy review PASS.

Contributors

Robby Czesany / robbyczgw-cla

Breaking Changes

Removed aliasing of `kilo_perplexity` and `perplexity`; they are now distinct providers (`kilo-perplexity` and native `perplexity`).
Changed default behavior: direct Perplexity usage now requires `PERPLEXITY_API_KEY` and routes to `https://api.perplexity.ai/chat/completions`, while Kilo gateway routing uses `KILOCODE_API_KEY` and `https://api.kilo.ai/api/gateway/chat/completions` under provider `kilo-perplexity`.
Existing configurations selecting `perplexity` with only `KILOCODE_API_KEY` must be updated to use explicit provider config `kilo-perplexity` or add a native `PERPLEXITY_API_KEY`.

View diff on GitHub

Weekly OSS security release digest.

The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.

No spam, unsubscribe anytime.

Share this release

Share on X Share on Bluesky

Track robbyczgw-cla/web-search-plus-mcp

Get notified when new releases ship.

About robbyczgw-cla/web-search-plus-mcp

Multi-provider web search with intelligent auto-routing (Serper, Tavily, Exa)

All releases →