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.

[Omi] Add configurable daily recap depth (Brief/Normal/Deep Reflection)

The current daily recap is too shallow and lacks important details. The user requests a configurable setting with three levels (Brief, Normal, Deep Reflection) to allow for more in-depth and meaningful daily recaps, addressing current limitations like item limits, word count, and lack of prioritization/emotional context.

Original Source

@@omi-discord-vector[bot] | 0 pts | 3d ago

## Problem The current daily recap feels shallow and doesn't capture the important parts of the day. The hard limits and "be snappy" directive optimize for brevity over depth, missing meaningful reflection. **Current limitations:** - Max 3-4 items per category - <15 words per item forced by prompt - No prioritization by user values/goals - No emotional context or patterns - No connections to past reflections ## Proposed Solution Add user-configurable recap depth setting with 3 levels: ### **Brief** (current behavior) - Max 3-4 items per category - <15 words per item - Fast skim, action-focused - 30-60 seconds to read ### **Normal** (balanced) - Max 5-8 items per category - 1-2 sentences per item - Key themes + context - 20-30 words per item - Connect related themes - 2-3 minutes to read ### **Deep Reflection** (thoughtful) - No hard limits (10-15+ items if valuable) - 2-4 sentences per item with context - Connections between conversations - Emotional/energy patterns - Links to pas

Discussion

Loading comments...