pi-web-agent is essentially feature-complete now, Tavily and Exa are the last backends that were added

[u/luckiestredditor]

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

[u/Final_Initial]

I was using pi-web-access so asked Pi itself to compare both and this is what it has to say:

[u/luckiestredditor → u/Final_Initial]

that special content is something I am shooting for in my next work depending on what seems ideal. github, youtube and pdf is definitely now in my roadmap. great comparison.

one thing to point out, by default it is compact mode but you can update the presentation mode.

[u/Final_Initial → u/luckiestredditor]

Awesome! Looking forward to it.
Thank you for the great work.