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.

[Outline] documents.update API: Add server-side find-and-replace (editMode: "find_replace")

Extend the `documents.update` API endpoint with a `find_replace` editMode to allow surgical edits to existing content without replacing the entire document body. This is needed for API integrations and LLM-powered workflows to avoid race conditions with live editors.

Original Source

@@NullSense | 5 pts | 25d ago

### Problem The `documents.update` endpoint currently supports three `editMode` values: `replace`, `append`, and `prepend`. These work well for full-document updates or adding new content, but there's no way to make **surgical edits to existing content** without replacing the entire document body. This creates a real problem for API integrations and LLM-powered workflows: 1. **Race conditions with live editors.** If a user is editing in the browser while an API client updates the document, the API client must fetch → modify → push the full text, overwriting any concurrent browser changes. 2. **Unnecessary revision noise.** A one-line fix creates a full-document revision, making revision history harder to audit. 3. **No atomic partial edits.** The workaround (fetch full text, string-replace client-side, push full text) is fragile and not atomic. ### Proposed Solution Add a new `editMode: "find_replace"` option to `documents.update`: ```json POST /api/documents.update { "id": "do

Discussion

Loading comments...