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.

[Tabby] Allow custom Katana configuration file or Developer Docs prefix URL

Provide options to customize Katana's behavior when indexing custom endpoints from the Developer Docs section. This could involve allowing a custom `config.katana.txt` or `config.katana.flags` file, or a per-URL configuration for Katana.

Original Source

@@theFra985 | 1 pts | 11/26/2025

Hi, I think it would be pretty helpful to be able to provide some customization to the katana behavior when indexing a custom endpoint provided in the Developer Docs section. The best solution would probably be to have a per-URL configuration that allows changing the katana behavior but looking at the current implementation I think an easy "fix" would be to allow specifying a custom prefix URL and, globally, allow creating an optional `config.katana.txt` or `config.katana.flags` alongside the config.toml file that gets loaded using katana's `--config` flag if detected. This would allow full customization of the katana behavior without increasing complexity of the current `WebCrawlerJob` implementation. **Additional context** See [katana config flag](https://github.com/projectdiscovery/katana/blob/6253b22ac5a90a7c5e2af870cf0c551cbc98c69d/cmd/katana/main.go#L130) and current [`crawl_url` implementation](https://github.com/TabbyML/tabby/blob/aa5d0e4cb73b77d74923c140a5030fd8ce32b34b/cra

Discussion

Loading comments...