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.

[Warp] Lifecycle hooks for local Oz agent conversations (before_agent_start / agent_end)

Add two lifecycle hooks to local Oz agent conversations — before_agent_start and agent_end — allowing MCP servers and Warp plugins to inject context before every response and trigger guaranteed automation.

Original Source

@@neoladin | 0 pts | 9d ago

### Pre-submit Checks - [x] I have [searched Warp feature requests](https://github.com/warpdotdev/warp/issues?q=is%3Aissue+label%3AFEATURE) and there are no duplicates - [x] I have [searched Warp docs](https://docs.warp.dev) and my feature is not there ### Describe the solution you'd like? Summary Add two lifecycle hooks to local Oz agent conversations — before_agent_start and agent_end — allowing MCP servers and Warp plugins to inject context before every response and trigger guaranteed automated actions after every conversation. This would unlock a class of integrations that are currently impossible or unreliable: persistent memory, automatic audit logging, context pre-loading, cost analytics, DLP scanning, and more — for every Warp user, not just advanced ones. ### Is your feature request related to a problem? Please describe. The Problem — "Instructed" vs "Guaranteed" Warp's current approach to automation is instructed: Rules and Skills tell the agent what to do, and it usu

Discussion

Loading comments...