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.

[Claudia] Add --dev mode to installer for daemon source-tree iteration

Contributors iterating on the memory daemon currently have to run `pip install -e` into the venv after every change to see the effect through the installer. This adds friction to the inner dev loop. Proposed Solution: Add a `--dev` flag to `claudia setup` to skip venv creation and streamline the development process.

Original Source

@@jonesrussell | 0 pts | 3/7/2026

## Problem Contributors iterating on the memory daemon currently have to run `pip install -e` into the venv after every change to see the effect through the installer. This adds friction to the inner dev loop. ## Proposed Solution Add a `--dev` flag to `claudia setup`: ```bash claudia setup --dev /path/to/project ``` In dev mode the installer: 1. Skips venv creation entirely 2. Finds system Python 3.10+ 3. Verifies `import claudia_memory` succeeds with `PYTHONPATH=<repo>/memory-daemon` 4. Writes `.mcp.json` with `env.PYTHONPATH` so Claude Code spawns the daemon from the local source tree each session 5. Runs the preflight check with the same Python + env (no venv path required) A new `getMemoryDaemonSrc()` helper resolves `memory-daemon/` relative to `bin/index.js` so the path is always correct regardless of where `claudia` is installed. ## Impact - Zero behaviour change when `--dev` is not passed - Eliminates the pip reinstall step for daemon contributors - `.mcp.json` written

Discussion

Loading comments...