Pi Web Access Files

Pi Web Access 0.29.0 adds more ways to search and extract content while making everyday use faster and more reliable. You can now search Google through SerpApi, use a self-hosted Crawl4AI instance for extraction fallback, and connect through SOCKS proxies. Curator can carry an auto-summary choice across searches in the same prompt, and 1Password service accounts now work with credential resolvers. This release also improves startup time and fixes several provider fallback, credential-routing, caching, and configuration issues.

Highlights

• Search Google through SerpApi with domain and recency filters.
• Use a self-hosted Crawl4AI instance as an extraction fallback.
• Connect through SOCKS proxies and resolve credentials with 1Password service accounts.
• Start Pi faster through on-demand loading of extraction and AI features.
• Get more reliable provider fallback, credential routing, caching, and config discovery.

Full changelog

Highlights

• Search Google through SerpApi with domain and recency filters.
• Use a self-hosted Crawl4AI instance as an extraction fallback.
• Connect through SOCKS proxies and resolve credentials with 1Password service accounts.
• Start Pi faster through on-demand loading of extraction and AI features.
• Get more reliable provider fallback, credential routing, caching, and config discovery.

Added

• Added a Curator action that approves the current summary and uses auto-summary for later default-workflow searches in the same prompt run. The choice is not saved between prompts. Thanks to @thomak-dev for issue [#376].
• Added a self-hosted Crawl4AI extraction fallback for fetch_content, configured with crawl4aiBaseUrl / CRAWL4AI_BASE_URL and crawl4aiApiToken / CRAWL4AI_API_TOKEN. It runs after Firecrawl and before hosted providers, and can be selected with crawl4ai in fetchRouting.providers. Thanks to @bergheim for PR [#375].
• Added an explicit SerpApi Google Search provider with serpapiApiKey / SERPAPI_KEY, domain and recency filters, search routing, and Curator support. Thanks to @tanysheng for PR [#363].
• Added SOCKS4, SOCKS4A, SOCKS5, and SOCKS5H proxy support in config and per-call overrides. Thanks to @phillipzink for PR [#365].
• Added 1Password service-account support for credential resolver commands through OP_SERVICE_ACCOUNT_TOKEN. Thanks to PR author @Avg8888 and commit author @xapids for PR [#364].

Changed

• Load extraction and AI features only when first used, reducing extension startup time. Thanks to @ducaoya for PR [#366].

Fixed

• Treat Tavily monthly plan exhaustion as a quota error so search routing can fall back to another provider. Thanks to @simbel for issue [#378].
• Refuse to send Pi-resolved OpenAI credentials to the official Responses endpoint when they belong to a provider with a custom baseUrl. Configure openaiResponsesUrl explicitly to search through a gateway. Thanks to @projectkite for issue [#367].
• Remove expired fetched content from memory when pruning the cache, while preserving the retrieval window and session history. Thanks to @MDGChamomile for issue [#362].
• Use Pi's agent directory (~/.pi/agent/web-search.json) for the default web-search config instead of falling back to the legacy ~/.pi/web-search.json. Existing PI_CODING_AGENT_DIR and XDG behavior is unchanged. Thanks to @lJoublanc for issue [#360].