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.

[Claude Code] Separate system prompt from user context window

The base system prompt (tool definitions, permissions, skills, etc.) is loaded into the user's context window every session, consuming valuable context space. User requests it to be separated.

Original Source

@@wiver7388-debug | 0 pts | 9h ago

### Preflight Checklist - [x] I have searched [existing requests](https://github.com/anthropics/claude-code/issues?q=is%3Aissue%20label%3Aenhancement) and this feature hasn't been requested yet - [x] This is a single feature request (not multiple features) ### Problem Statement ## Problem The base system prompt (tool definitions, permission rules, skill listings, MCP server instructions, plan mode instructions, etc.) is loaded into the **user's context window** every session. This consumes a significant portion of the available context before the user even sends their first message. ### Observed impact - In a **non-coding, document-only project**, the system prompt (tool schemas, coding-specific rules, skill listings) still occupies ~25% of the context window. - Even after aggressively disabling MCP servers, skills, and hooks via project-level `settings.json`, the reduction is marginal because the **core system prompt itself is large and unavoidable**. - Users experience repeated

Discussion

Loading comments...