TRACEABLE OPEN-SOURCE DEMAND SIGNALS

Opportunity Radar

We scan public GitHub Issues for recurring requests, workflow friction and missing capabilities—then rank the strongest signals without hiding the original evidence.

62 signals · Last data refresh Nov 20, 2026, 11:30 PM UTC

ISSUE SCAN COVERAGE35 / 36 current repositories · 5 new

“New” means first detected by the Radar within 48 hours. Live opportunities come only from projects in the current curated feed; archived projects remain searchable as historical research but cannot leave stale demand signals here.

Demand confidence
Professional field
Problem theme
Evidence signal, not proof of market demand.

A popular Issue can reveal real friction, but it does not prove willingness to pay. Use these leads for interviews, validation and product discovery.

FROM SIGNAL TO ACTION

A 3-step validation sprint

Use the evidence as a starting point, then verify the problem before building.

  1. 1. Read the threadIdentify who has the problem and the workaround they use today.
  2. 2. Contact five usersAsk about frequency, cost and what they already tried.
  3. 3. Test one narrow fixOffer a manual or lightweight solution before writing a full product.
7 qualified signals
#1
Tool execution & lifecycle · ResearchREPEATED ACROSS 3 PROJECTS

Support dynamic tool addition/removal after agent creation and in middleware

Observed in langchain-ai/langchain · Python · MIT

What the reporter described: Checked other resources [x] This is a feature request, not a bug report or usage question. [x] I added a clear and descriptive title that summarizes the feature request. [x] I used the GitHub search to find a similar feature request and didn't find it. [x] I checked the LangChain documentation and API reference to see…

Related friction appears in 3 independent repositories. This is stronger than one backlog item, but still requires direct user validation.

19 comments16 positive reactions382 days openEvidence score 89/100Project Radar 97
langchainfeature requestcandidateexternal
#2
Provider interoperability · ResearchREPEATED ACROSS 11 PROJECTS

The batch method from ChatModels and all the Runnables does not really support the OpenAI batch API.

Observed in langchain-ai/langchain · Python · MIT

What the reporter described: Checked other resources [X] I added a very descriptive title to this issue. [X] I searched the LangChain documentation with the integrated search. [X] I used the GitHub search to find a similar question and didn't find it. [X] I am sure that this is a bug in LangChain rather than my code. [X] The bug is not resolved…

Related friction appears in 11 independent repositories. This is stronger than one backlog item, but still requires direct user validation.

17 comments37 positive reactions717 days openEvidence score 89/100Project Radar 97
help wantedopenaiexternal
#3
Tool & system connectors · ResearchREPEATED ACROSS 8 PROJECTS

Feature Request: Pass `_meta` parameter through to MCP SDK `call_tool()`

Observed in langchain-ai/langchain · Python · MIT

What the reporter described: Problem When invoking MCP tools via , the parameter is not passed through to the MCP SDK's method, even though: The MCP SDK already supports it - accepts as a keyword argument The MCP specification (2025-06-18) defines as a reserved field for attaching metadata to requests This prevents users from leveraging MCP's…

Related friction appears in 8 independent repositories. This is stronger than one backlog item, but still requires direct user validation.

16 comments10 positive reactions300 days openEvidence score 85/100Project Radar 97
externalmcp
#4
Product Capability workflows · ResearchREPEATED ACROSS 13 PROJECTS

[FEAT] Add deterministic pre-action authorization at the tool-call hook level

Observed in VoltAgent/voltagent · TypeScript · MIT

What the reporter described: Is your feature request related to a problem? Please describe. VoltAgent's guardrail system validates content but doesn't deterministically authorize tool execution before it happens. With MCP servers proliferating, agents face silent injection risks where a poisoned prompt triggers unintended tool calls. The Open…

Related friction appears in 13 independent repositories. This is stronger than one backlog item, but still requires direct user validation.

23 comments10 positive reactions246 days openEvidence score 81/100Project Radar 89
enhancement
#5
Failure recovery · ResearchREPEATED ACROSS 3 PROJECTS

[Bug]: Memory Leak on Repeated /md Requests via Docker (MacOS) — Container Crashes Randomly Over Time

Observed in unclecode/crawl4ai · Python · Apache-2.0

What the reporter described: crawl4ai version 0.6.0-r2 or Latest docker image Expected Behavior When sending repeated POST requests to /md every 10 seconds with dynamic URLs, the Docker container should handle each request efficiently without memory leaks or crashes, maintaining stable memory usage over time. Current Behavior Initially,…

Related friction appears in 3 independent repositories. This is stronger than one backlog item, but still requires direct user validation.

15 comments7 positive reactions510 days openEvidence score 79/100Project Radar 100
❓ Question🐳 Docker
#6
Tool & system connectors · ResearchREPEATED ACROSS 8 PROJECTS

Bring Docker API server to feature parity with Crawl4AI v0.7.x

Observed in unclecode/crawl4ai · Python · Apache-2.0

What the reporter described: Description The Docker API server lags behind the Python library. This issue tracks adding endpoints/parameters to expose the following library features: 1. Adaptive crawling AdaptiveCrawler, AdaptiveConfig, CrawlState, CrawlStrategy, StatisticalStrategy Missing: endpoints to run/tune adaptive crawls 2. C4A Script…

Related friction appears in 8 independent repositories. This is stronger than one backlog item, but still requires direct user validation.

3 comments4 positive reactions449 days openEvidence score 66/100Project Radar 100
✨ Enhancement⚙️ Under Review
#7
Product Capability workflows · ResearchREPEATED ACROSS 13 PROJECTS

[Bug]: When extracting data with scroll_full_page, only the final elements get parsed

Observed in unclecode/crawl4ai · Python · Apache-2.0

What the reporter described: crawl4ai version 0.4.248 Expected Behavior I'm crawiling Twitter, specifically the "following" section of a profile. I have a css selector for the relevant data (user's names and bios) and set up a JsonCssExtractionStrategy. If I don't use scroll full page, I understandably only expect to get the first N user…

Related friction appears in 13 independent repositories. This is stronger than one backlog item, but still requires direct user validation.

22 comments0 positive reactions638 days openEvidence score 63/100Project Radar 100
🐞 Bug⚙️ In-progress

How opportunities are ranked

The evidence score combines capped, diminishing-return discussion, positive reactions, unresolved duration and the underlying project’s Radar Score. This prevents one repeatedly commented thread from overwhelming independent signals. Maintenance-only tickets, dependency dashboards, CI failures and release checklists are filtered out. Rankings are independent and never paid placements.