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.

[Claude Mem] Implement branch-scoped memory with Git ancestry filtering

Tag observations with branch and commit_sha at write time and filter SessionStart context and MCP search results to only show observations from commits that are ancestors of the current HEAD. Include graceful degradation for non-git directories, detached HEAD, and shallow clones.

Original Source

@@thedotmack | 0 pts | 1d ago

**Type:** feature / enhancement request (re-filed from maintainer's own PR during backlog cleanup) ## Summary - **Branch-scoped observations**: Observations are tagged with `branch` and `commit_sha` at write time via `detectCurrentBranch` in the hook layer - **Git ancestry filtering**: SessionStart context and MCP search results are filtered to only show observations from commits that are ancestors of the current HEAD - **Graceful degradation**: Non-git directories, detached HEAD, shallow clones, and resolution errors all fall back to showing all observations (no data loss) ## Implementation (6 phases) | Phase | What | |-------|------| | 01 | Schema migration (`branch`/`commit_sha` columns), `detectCurrentBranch`, write path through `storeObservation` | | 02 | `resolveVisibleCommitShas` git ancestry utility with `git merge-base --is-ancestor` batching | | 03 | SessionStart `ContextBuilder.generateContext()` filters observations by branch ancestry | | 04 | MCP search `SearchManager.

Discussion

Loading comments...