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.

[smcraft] Use as collaborative design surface

The intent is to use smcraft as a collaborative design surface, allowing two agent instances to co-model a state machine via the MCP, with the web frontend providing shared visual feedback before code generation.

Original Source

@@miadisabelle | 0 pts | 8d ago

## Context `jgwill/smcraft` currently ships four packages: `mcp/` (MCP server), `web/` (Next.js frontend), `ts/` (TypeScript runtime), `py/` (Python runtime). The intent surfaced in this stream is to use smcraft as a **collaborative design surface** — two agent instances co-modeling a state machine via the MCP, with the `web/` providing shared visual feedback — before any code is generated. The target workload is the `miaco decompose` chain (source: `/src/mia-code/miaco`). This chain is an evolved, LangChain-style sequenced variant of `mcp-pde`: instead of a single decomposition, a ceremony-opening triggers a multi-step chain whose states, transitions, and artefacts need to be made explicit. This work deliberately does not rush to code. Non-code artefacts (state-machine definitions, RISE specs, diagrams, ceremony scripts) are first-class outputs of smcraft. PDE decomposition for this workstream: `.pde/2604151042--bd032999-1f74-4bb6-a93c-6f9d959c7c26/`. ## Desired State - `mcp/` s

Discussion

Loading comments...