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.

[QMD] Make maxContextChars configurable

Allow users to customize the context length limit, currently hardcoded to 900 tokens, via an environment variable or config file setting. This would provide flexibility for users with larger documents or different chunk strategies.

Original Source

@@MetroLee | 0 pts | 3/15/2026

Currently the context length limit is hardcoded to 900 tokens. For users with larger documents or different chunk strategies, it would be useful to allow customization via: - Environment variable: `QMD_MAX_CONTEXT_CHARS` - Or config file setting This would give users flexibility without needing wrapper scripts. **Use case:** We need to increase this limit for better contextual retrieval in our agentic workflow. **Expected behavior:** Users can set a custom value via environment variable or config to override the default 900 token limit. **Workaround (current):** Using wrapper scripts that patch the binary on each invocation, which is fragile and adds overhead. Thank you for considering this feature!

Discussion

Loading comments...