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.

[Open Codesign] Define roadmap for OpenCode/Codex/CCS style configuration imports

Establish a clear roadmap for integrating external coding-tool API configurations, specifically for OpenCode, Codex, and CCS styles, ensuring a unified capability story for imported configurations and defining the integration approach for CCS.

Original Source

@@Sun-sunshine06 | 0 pts | 6d ago

# [Feature]: 跟进 OpenCode / Codex / CCS 风格配置导入路线 / Follow up OpenCode-Codex-CCS style import roadmap ## Problem / pain point / 问题 OpenCode 和 Codex 导入已经存在，但“外部 coding-tool API 配置”作为产品能力，路线还不够清晰。还有两个空缺： - imported config 还没有统一的 capability story - `CCS` 在当前语境里的具体含义与目标接入形态仍不明确 We need a clearer roadmap for external coding-tool API configs, especially before building anything CCS-specific. ## Proposed solution / 方案做一个 research-first follow-up，明确： - 我们打算支持哪些外部配置来源 - import fidelity 分级是什么 - `CCS` 在这里到底是 config source、gateway、还是更广义集成 - 如果确认要支持 CCS，下一步应拆成哪些实现 issue Deliverable: a short decision note plus concrete follow-up issues. ## Alternatives considered / 备选方案 - 不澄清语义，直接实现 CCS - 风险是又做成一个 one-off importer ## Scope / 范围 Provider / model ## Acceptance criteria / 验收标准 - 明确 `CCS` 在当前路线中的定义 - 决定 CCS 属于 import adapter、provider preset 还是 gateway integration - 明确 OpenCode / Codex import 的支持边界 - 如需实现，拆出后续 concrete issues ## Likely touchpoints / 可能涉及 - `apps/desktop/src/main/import

Discussion

Loading comments...