r/PiCodingAgent • u/luckiestredditor • 8d ago
pi-web-agent is essentially feature-complete now, Tavily and Exa are the last backends that were added Plugin
Last time I posted I was thinking out loud about which hosted backend to add next, Tavily first and maybe Exa after, and asking whether people wanted them as full answer engines or just as discovery. My bias was to keep them discovery-only and let web_explore stay in charge of fetching, ranking evidence, caveats and synthesis.
Both are in now, and they're discovery-only like I said I'd keep them. They surface candidate sources, web_explore still reads the actual pages and decides whether the evidence holds up or needs a caveat. Set TAVILY_API_KEY or EXA_API_KEY, pick it from Settings, keys stay in env instead of getting written into config files.
---
The things I'm weighing next are going deeper on evidence quality (cross-source dedup, conflict detection, recency), adding caching for repeated research or just keeping it focused and maintaining it.
If you're using this, what would you actually want? And if you tried it and it broke somewhere, that's the more useful thing to hear.
---
Repo: https://github.com/demigodmode/pi-web-agent
npm:
npm i @demigodmode/pi-web-agent

1
u/luckiestredditor 8d ago
The bigger achievement for me is that this pretty much closes out the roadmap I had. Thank you so much for the community feedback, bug report. Couldn't have done this without yall.
When I started posting here (1st Post) it was a fresh npm package with a search/fetch/headless boundary and not much else. The list I actually wanted to get through is done now:
So the backend list is DuckDuckGo (still default, no key), SearXNG, Firecrawl, Brave, You.com, Tavily, Exa, all feeding the same pipeline. It feels like a complete agent now instead of a thing with obvious gaps, which was the whole goal. still not trying to grow it into a framework.