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.

[Claude Mem] Add cooperative cycling and Storyline content ingestion engine

Replace abort-based session cycling with MCP custom tools (cycle_status, complete_cycle) that allow agents to decide when to cycle based on context pressure. Implement a ContentIngestionRunner for sequential file-by-file content ingestion with SQLite progress tracking, content hash deduplication, and cancellation support, along with StorylineRoutes for HTTP API.

Original Source

@@thedotmack | 0 pts | 1d ago

**Type:** feature / enhancement request (re-filed from maintainer's own PR during backlog cleanup) ## Summary - **Cooperative cycling**: Replace abort-based session cycling with MCP custom tools (`cycle_status`, `complete_cycle`) that let the agent decide when to cycle based on context pressure - **ContentIngestionRunner**: Sequential file-by-file content ingestion orchestrator with SQLite progress tracking, content hash dedup, and cancellation support - **StorylineRoutes**: HTTP API (`POST /run`, `GET /status`, `POST /cancel`) for the Storyline skill to drive content ingestion from the engine ### New files | File | Purpose | |------|---------| | `EndlessModeToolServer.ts` | MCP tool server with `cycle_status` and `complete_cycle` for cooperative cycling | | `ContentIngestionRunner.ts` | File-by-file ingestion orchestrator with observer pipeline integration | | `StorylineRepository.ts` | SQLite CRUD for `storyline_runs` and `storyline_files` tables | | `StorylineRoutes.ts` | Express

Discussion

Loading comments...