Pi Web Access now starts fresh sessions with a smaller tool list, and you can bring in your configured web tools with web_enable when you need them. Long searches are easier to read while the complete results remain available for follow-up. You can also search with Baizhi MCP when you choose it as a provider. Local Brave, Exa, and Tavily services now work over HTTP on loopback addresses without relaxing the HTTPS requirement for remote hosts.
Highlights
- Keep fresh sessions focused until you need web tools.
- Read shorter search responses and retrieve the full results when needed.
- Choose Baizhi MCP for web searches.
- Connect Brave, Exa, and Tavily to local HTTP services.
Need to know
In supported fresh sessions, call web_enable before using the other web tools. Existing sessions and environments without lazy activation retain their current tool behavior.
Full changelog
Highlights
- Start fresh sessions with a smaller web-tool list, then enable the tools when you need them.
- Keep long search responses manageable without losing access to the full results.
- Search with Baizhi MCP when you explicitly configure it.
- Connect Brave, Exa, and Tavily to local HTTP services on loopback addresses.
Added
- Fresh sessions now show
web_enableinstead of the full web-tool list when supported. Call it to make your configured web tools available. Thanks to @Knimoms for PR #424. - Added Baizhi MCP as an optional search provider, with search routing and Curator support. It is used only when explicitly selected. Thanks to @ct-jaryn for PR #422.
Changed
- Long
web_searchresponses now show a shorter result and the providers used. Full results remain available throughget_search_content. Thanks to @theSprog for issue #423.
Fixed
- Allow explicitly configured Brave, Exa, and Tavily API base URLs to use HTTP on true loopback hosts while continuing to require HTTPS remotely. Thanks to @aaschmid for issue #421.