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.

[Selenium] Add APIRequestContext for HTTP requests with shared browser cookie/auth state

Selenium currently has no way to make HTTP API calls that share authentication/cookie state with the browser session. This is a significant gap compared to Playwright's APIRequestContext, which is one of the most-used features in modern test automation. This would allow for fast test setups by logging in via API to get auth cookies and using those cookies in the browser to skip slow UI login flows.

Original Source

@@mayank-at-sauce | 0 pts | 3/14/2026

### Description The problem this would solve: Selenium currently has no way to make HTTP API calls that share authentication/cookie state with the browser session. This is a significant gap compared to Playwright's APIRequestContext, which is one of the most-used features in modern test automation. Common real-world scenarios that require this: 1. Fast test setup — Log in via API (POST /auth/login) to get auth cookies, then use those cookies in the browser to skip slow UI login flows 2. API + UI hybrid testing — Verify a UI action triggers the correct backend state (e.g., click "Delete" button, then call GET /api/items to confirm deletion) 3. Test data seeding — Create test fixtures via API before browser tests, sharing the same authenticated session 4. Backend assertion — After a browser interaction, assert API responses without opening new pages Today, users must manually extract cookies from driver.get_cookies(), construct a separate requests.Session, and hand

Discussion

Loading comments...