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 WebUI] Register memory tools for models with memory capabilities

When a model has capabilities.memory set to true, the tools for memory functions should be registered automatically in the chat request. This will prevent tool loops and ensure that memory functions can be executed properly.

Original Source

@@Thump604 | 0 pts | 3/14/2026

## Bug Description When a model has `capabilities.memory: true` in its meta config and the system prompt instructs the model to use `add_memory`/`search_memories`, the model generates tool calls for these functions. However, the tools are not registered for execution because `get_builtin_tools()` in `utils/tools.py` requires `features.get("memory")` to be truthy — which depends on the frontend sending `features: {memory: true}` in the chat request. This creates a tool loop: the model calls `add_memory`, but since the tool isn't registered (`tool_function_name not in tools`), the result is empty, and the model retries up to `CHAT_RESPONSE_MAX_TOOL_CALL_RETRIES` (30) times. ## Steps to Reproduce 1. Configure a model with `capabilities.memory: true` in the model editor 2. Set a system prompt that tells the model to use `add_memory` for preferences 3. Set `function_calling: native` in model params 4. Start a new chat with this model 5. Send: "Remember my favorite color is blue" 6. The

Discussion

Loading comments...