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
Context & memory boundaries · Agent InfrastructureREPEATED ACROSS 4 PROJECTS

Feature Request: Team, agent, and memory-level access control

Observed in vectorize-io/hindsight · Python · MIT

What the reporter described: Summary I would like to request a discussion around a more detailed permission and sharing model for the open-source Hindsight server. The current OSS authorization model seems intentionally simple: : one shared API key mapped to the configured schema. : one Supabase user JWT mapped to a schema derived from that…

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

3 comments10 positive reactions157 days openEvidence score 76/100Project Radar 97
core
#2
Context & memory boundaries · Agent InfrastructureREPEATED ACROSS 4 PROJECTS

Hard-coded `new InMemoryRunner(...)` prevents injection and custom runner implementations

Observed in google/adk-java · Java · Apache-2.0

What the reporter described: In the current implementation of , the runner instance is created directly via constructor: This introduces a structural limitation: the code forces a specific runner implementation and does not allow the caller to provide their own or override behaviour. Why this is problematic No ability to inject alternative Runner…

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

6 comments5 positive reactions351 days openEvidence score 72/100Project Radar 89
needs review
#3
Tool & system connectors · Agent InfrastructureREPEATED ACROSS 8 PROJECTS

adk-dev capability supports rapid integration as a Spring Starter for SpringBoot Apps

Observed in google/adk-java · Java · Apache-2.0

What the reporter described: Currently, the Dev UI debugging capability must be launched in Maven format. Considering the convenience of integrating capabilities into a large number of Spring Boot applications, the related code within Dev needs to be refactored and layered, while also providing a Starter component for rapid integration with…

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

13 comments3 positive reactions529 days openEvidence score 69/100Project Radar 89
help wantedneeds review
#4
Provider interoperability · Agent InfrastructureREPEATED ACROSS 11 PROJECTS

feat: Add support for OpenAI-compatible LLM endpoints (Groq, Ollama, Azure OpenAI, etc.)

Observed in google/adk-java · Java · Apache-2.0

What the reporter described: 🔴 Required Information Is your feature request related to a specific problem? Yes. Currently, ADK-Java only supports Google's Gemini and Claude models out of the box. Developers cannot easily use other LLM providers that implement the OpenAI Chat Completions API format, such as: Groq (fast inference with open models)…

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

11 comments3 positive reactions188 days openEvidence score 68/100Project Radar 89
needs review
#5
Tool & system connectors · Agent InfrastructureREPEATED ACROSS 8 PROJECTS

coding-agents: per-message temporal provenance collapses to the conversation timestamp

Observed in vectorize-io/hindsight · Python · MIT

What the reporter described: Bug description The current Codex reader preserves source message timestamps, but automatic retention groups the conversation into one item whose API timestamp is the first message's timestamp. This collapses message-level temporal provenance into a conversation-level clock. Source timestamp preservation and…

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

5 comments1 positive reactions47 days openEvidence score 65/100Project Radar 97
integration:coding-agents
#6
Context & memory boundaries · Agent InfrastructureREPEATED ACROSS 4 PROJECTS

Smarter json chunking to prevent loss of critical context

Observed in vectorize-io/hindsight · Python · MIT

What the reporter described: Use Case I'm using hindsight to ingest agent session files as jsonl. Problem Statement I think that #2113 and #2409 are notable improvements for extraction. There are still some cases where single messages are so long they will be above HINDSIGHT API RETAIN STRUCTURED CHUNK SIZE and split. Take this example jsonl: If…

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

4 comments1 positive reactions140 days openEvidence score 65/100Project Radar 97
enhancementcore
#7
Product Capability workflows · Agent InfrastructureREPEATED ACROSS 13 PROJECTS

Terminal.run_command() hangs indefinitely on Linux/WSL2 — end-of-command marker never yielded from splitlines/tuple-unpack

Observed in FoundationAgents/MetaGPT · Python · MIT

What the reporter described: Summary hangs indefinitely on Linux/WSL2 whenever the persistent shell's stdout ends with the end-of-command marker as the final line (i.e., always, under normal conditions). The read loop in uses after reading each byte, but when the buffer contains exactly one -terminated line, the tuple-unpacking idiom moves that…

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

6 comments0 positive reactions124 days openEvidence score 56/100Project Radar 76
inactive

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.