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.

[PostHog] Support workflows as code with Git versioning

The existing no-code workflow builder is insufficient for teams that prefer to manage workflows as code, with Git versioning, AI-friendly editing, and programmatic control via the Workflows MCP.

Original Source

@@meikelmosby | 0 pts | 3d ago

### Feature request ## Feature Request: Code-Based Workflows with Git Versioning, AI Support & MCP Integration ### Summary Support defining workflows as code (e.g. YAML/JSON/SDK) stored in repositories with Git versioning and AI-friendly editing, leveraging the Workflows MCP for programmatic management, with an option to choose whether the UI or code is the source of truth. --- ### Problem The current no-code builder is a great starting point, but creates friction for teams that primarily work in code: - Workflows are not version-controlled alongside the rest of the product - Changes cannot go through standard PR/review processes - Hard to leverage AI tools (e.g. Claude Code) effectively - Limited integration with existing developer workflows and tooling - No clear ownership model between UI-edited vs programmatically managed workflows --- ### Proposed Solution Introduce support for defining workflows as code, building on top of the existing Workflows MCP, with explicit source-of

Discussion

Loading comments...