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] Implement Layer 3 transcript storage and TITANS observer

Implement get_transcript_segment MCP tool for retrieving original conversation context from ChromaDB via observation IDs. Introduce a TITANS conversation observer for fire-and-forget background analysis, producing seven observation types (e.g., emotional_signal, overconfidence, frustration).

Original Source

@@thedotmack | 0 pts | 1d ago

**Type:** feature / enhancement request (re-filed from maintainer's own PR during backlog cleanup) ## Summary - **Layer 3 transcript storage**: `get_transcript_segment` MCP tool for retrieving original conversation context from ChromaDB, traversal-only via observation IDs - **TITANS conversation observer**: Fire-and-forget background analysis producing 7 observation types (emotional_signal, overconfidence, frustration, pattern_recognition, etc.) - **Progressive search MCP fix**: Dynamic type system for 3-layer search workflow (search → get_observations → get_transcript_segment) - **Build fixes**: Replaced `glob` with `Bun.Glob` to fix lru-cache/CJS incompatibility, added `bun` to esbuild externals, fixed `OneShotQuery` EnvManager import ## Files changed - `src/services/sync/ChromaSync.ts` — transcript Chroma methods - `src/services/transcripts/processor.ts` — conversation exchange tracking, flush to Chroma - `src/services/worker/http/routes/SessionRoutes.ts` — Layer 3 HTTP handlers -

Discussion

Loading comments...