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.

[Everything Claude Code] Add ECC install-state plus uninstall / doctor / repair lifecycle

ECC has no canonical installed-state record, making uninstall and repair nondeterministic. A durable install-state contract is needed to manage the lifecycle of installed modules.

Original Source

@@affaan-m | 0 pts | 3/13/2026

## Problem ECC has no canonical installed-state record. That makes uninstall, repair, and post-install inspection nondeterministic. Today the repo can classify installable content, but it still cannot reliably answer: - what profile/modules were installed - what target they were installed into - what paths ECC owns - how to remove or repair only ECC-managed files Without install-state, lifecycle commands are guesswork. ## Scope Introduce a durable install-state contract and the first lifecycle commands: - `ecc list-installed` - `ecc uninstall` - `ecc doctor` - `ecc repair` Suggested state locations: - Claude: `~/.claude/ecc/install-state.json` - Cursor: `./.cursor/ecc-install-state.json` - Antigravity: `./.agent/ecc-install-state.json` The state file should capture at minimum: - installed version - timestamp - target - profile - resolved modules - copied/managed paths - source repo version or package version ## Non-Goals - Rebuilding the installer architecture from scratch

Discussion

Loading comments...