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.

[Codex] Terminal hyperlink support for file references

I'd like Codex CLI to support clickable file references in terminal output as an opt-in feature, rather than always rendering them as plain text. This would make file paths directly clickable in terminals.

Original Source

@@danarnold | 0 pts | 3/2/2026

### What variant of Codex are you using? CLI ### What feature would you like to see? I'd like Codex CLI to support clickable file references in terminal output as an opt-in feature, rather than always rendering them as plain text. In particular, it would be useful if Codex could optionally emit OSC 8 hyperlinks for local file references that it already prints in responses, using the configured `file_opener` scheme when available. This would make file paths directly clickable in terminals that support hyperlinks. I’d also like an additional opt-in mode for WSL users who open files through VS Code or VS Code Insiders running on Windows. In that setup, a plain `vscode://file/...` or `vscode-insiders://file/...` link is often not enough, because the editor is attached to the WSL environment rather than opening Linux paths as normal local Windows files. A WSL-aware mode could instead generate `vscode-remote` URLs based on the active distro, for example using `WSL_DISTRO_NAME`. The WSL

Discussion

Loading comments...