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.

[Continue] Add documentation for CLI hooks system

There is a comprehensive hooks system for CLI event interception that needs user-facing documentation. This documentation should cover core concepts and supported event types.

Original Source

@@continue[bot] | 0 pts | 3/14/2026

## Summary PR #11029 added a comprehensive hooks system for CLI event interception. This is a significant feature that allows external handlers (shell commands, HTTP endpoints) to intercept and respond to CLI events. However, there is no user-facing documentation for this feature. ## What needs to be documented The hooks system should be documented in a new page in the CLI section (`docs/cli/`), covering: ### Core Concepts - What hooks are and when to use them - Supported event types (16+ event types including tool execution, message handling, etc.) - Hook types: command (shell) and HTTP handlers ### Configuration - Config file locations and precedence: - `~/.claude/settings.json`, `~/.continue/settings.json` (user-global) - `.claude/settings.json`, `.continue/settings.json` (project) - `.claude/settings.local.json`, `.continue/settings.local.json` (project-local) - Regex-based event matching - The `disableAllHooks` option ### Hook Behavior - Exit code semantics (0 = procee

Discussion

Loading comments...