RequestHunt is a community-driven platform that collects and curates feature requests from X (Twitter), Reddit, and GitHub. We help product teams discover what features real users are asking for, making it easier to validate product ideas and prioritize feature development based on actual user demand.

How does RequestHunt collect feature requests?

RequestHunt uses AI-powered extraction to automatically collect feature requests from social media platforms including X, Reddit, and GitHub. The platform monitors discussions, issues, and posts to identify genuine user feature requests, extracting key information like the requested feature, product mentioned, and user sentiment.

Who uses RequestHunt?

RequestHunt is used by product managers, founders, developers, and product teams who want to discover what features real users are requesting. It's particularly valuable for startups looking to validate ideas, established companies prioritizing their roadmap, and developers building products that solve real user problems.

Is RequestHunt free to use?

Yes, browsing and searching feature requests on RequestHunt is completely free. We also offer API access for developers who want to integrate feature request data into their own applications. Check our pricing page for API plan details.

How often is RequestHunt data updated?

RequestHunt continuously collects feature requests from Reddit, X (Twitter), GitHub, YouTube, LinkedIn, and Amazon. You can also trigger on-demand scraping via the API or web interface to get the freshest data for any topic.

[LEANN] Verify dual-source routing for ReAct agent

Ensure that the ReAct agent correctly routes between local and web sources based on the query, verifying the full pipeline works for both paths.

Original Source

@@ASuresh0524 | 0 pts | 3/11/2026

## Context PR #232 added web search and page visit capabilities to the ReAct agent, giving it three tools: - `leann_search("query")` — local knowledge base - `web_search("query")` — public internet via Serper API - `visit_page("url")` — fetch full page content via Jina The PR is merged, but we haven't verified end-to-end that the agent correctly **routes between local and web sources** depending on the query, and that the **full pipeline** (retrieve → format → present) works for both paths. ## What to test ### 1. Dual-source presence - [ ] Confirm that when both `SERPER_API_KEY` is set and a local index exists, the agent has access to all three tools - [ ] Confirm that when `SERPER_API_KEY` is **not** set, `web_search` returns a clear error and the agent falls back to `leann_search` ### 2. Routing behavior - [ ] Query that should hit **local only** (e.g., "How does our authentication work?") → agent should choose `leann_search` - [ ] Query that should hit **web only** (e.g., "What

Discussion

Loading comments...