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), and GitHub. You can also trigger on-demand scraping via the API or web interface to get the freshest data for any topic.

[Archon] Improve knowledge crawl to filter irrelevant chunks

Enhance the knowledge crawl mechanism to intelligently filter out irrelevant chunks (e.g., headers, footers, side content, discussion links) from crawled URLs. The current crawl grabs everything, leading to many useless chunks and requiring manual workarounds.

Original Source

@@mythologique | 3 pts | 9/23/2025

Even requesting a knowledge crawl at level one on a URL results in many useless chunks, including things like headers, footers, side content, forum/discussion links, etc. The crawl isn't smart and just grabs everything, resulting in sometimes hundreds of useless chunks. My current solution has been to "print" relevant pages into PDFs, combine all the PDFs into one, convert the combined PDF using Docling into a .md to use with Archon. Below is a chunk, with a broken end link due to chunking, just showing links to Tauri releases. It provides no relevant information to use in a coding project. `0-beta.2 ](https://tauri.app/release/tauri/v2.0.0-beta.2/) * [ 2.0.0-beta.1 ](https://tauri.app/release/tauri/v2.0.0-beta.1/) * [ 2.0.0-beta.0 ](https://tauri.app/release/tauri/v2.0.0-beta.0/) * [ 2.0.0-alpha.21 ](https://tauri.app/release/tauri/v2.0.0-alpha.21/) * [ 2.0.0-alpha.20 ](https://tauri.app/release/tauri/v2.0.0-alpha.20/) * [ 2.0.0-alpha.19 ](https://

Discussion

Loading comments...