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.
8 Product Capability signals
#1
Provider interoperability · CodingREPEATED ACROSS 11 PROJECTS

Add gemini-3.1-pro-preview

Observed in google-gemini/gemini-cli · TypeScript · Apache-2.0

What the reporter described: What happened? gemini-3.1-pro-preview isn't in the models list What did you expect to happen? gemini-3.1-pro-preview is in the models list Client information <details <summary Client Information</summary Run to enter the interactive CLI, then run the command. </details Login information Google account Anything else we…

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

127 comments110 positive reactions274 days openEvidence score 91/100Project Radar 100
priority/p1area/enterprisekind/customer-issue🔒 maintainer only
#2
Tool execution & lifecycle · CodingREPEATED ACROSS 3 PROJECTS

Still can't figure out how to get v3 to actually perform work.

Observed in ruvnet/ruflo · TypeScript · MIT

What the reporter described: First off, let me commend the contributors for an amazing, product, and from what I see in the v3 docs, this looks like a pretty fantastic rewrite. But to be honest, I've been very confused when trying to use v3. Should it have command compatibility with 2.7.x to some degree? I'm able to spawn a hive mind or start a…

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

19 comments2 positive reactions307 days openEvidence score 79/100Project Radar 100
#3
Product Capability workflows · CodingREPEATED ACROSS 13 PROJECTS

analyst agent is never 'found'

Observed in ruvnet/ruflo · TypeScript · MIT

What the reporter described: I've noticed this a number of times now, using r88 analyst(Analyze VSDX format) ⎿ Initializing… ⎿ Error: Agent type 'analyst' not found. Available agents: general-purpose, api-docs, cicd-engineer, tdd-london-swarm, production-validator, backend-dev, pseudocode, specification, refinement, architecture, ml-developer,…

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

10 comments6 positive reactions471 days openEvidence score 79/100Project Radar 100
#4
Human approval & safety · CodingREPEATED ACROSS 2 PROJECTS

Seats blocked on a permission prompt (needs_input) don't raise rig attention or any watchdog alert

Observed in mvschwarz/openrig · TypeScript · Apache-2.0

What the reporter described: Summary A seat blocked on a runtime permission prompt is detected per-seat ( / ) but that signal never reaches anyone: the rig-level attention count ignores it and no watchdog policy can fire on it. In practice a Claude Code seat sat on a tool-approval prompt for 1.5 h in a 6-seat rig with an orchestrator and an…

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

16 comments1 positive reactions54 days openEvidence score 71/100Project Radar 96
bugarea: status-tuiconfirmed
#5
Tool execution & lifecycle · CodingREPEATED ACROSS 3 PROJECTS

Feature Request: Support agent.pause() within tool calls

Observed in browser-use/browser-use · Python · MIT

What the reporter described: What is the problem that your feature request solves? Feature request: human-in-the-loop pause that suspends Problem There is no first-class way for a tool to pause the agent, wait for external input (a human clarification, an approval, a signal from another process), and then resume — without falling foul of . The…

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

20 comments0 positive reactions198 days openEvidence score 70/100Project Radar 99
NEW SIGNALenhancement
#6
Product Capability workflows · CodingREPEATED ACROSS 13 PROJECTS

[FEAT] Multiple Claude Accounts

Observed in 777genius/agent-teams-ai · TypeScript · AGPL-3.0

What the reporter described: Summary We have multiple claude teams as a solution to prevent huge cost. A developer can have multiple premium seats, even in the same team with another e-mailadres. Problem It seems the claude provider only supports one user session. Area Provider runtime: Claude Describe the solution you'd like Allow multiple login…

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

6 comments3 positive reactions66 days openEvidence score 68/100Project Radar 90
enhancement
#7
Product Capability workflows · CodingREPEATED ACROSS 13 PROJECTS

Stall checks miss unsubmitted wakes and flag waiting or working seats

Observed in mvschwarz/openrig · TypeScript · Apache-2.0

What the reporter described: OpenRig version 0.6.3, commit . OS, Node and tmux versions Debian 13 under WSL2, Node 24.21.0, tmux 3.7c. Node and tmux versions were read back while preparing this draft on 2026-10-01. Harnesses involved Claude Code and Codex. What you ran and what happened Our local intake records two missed stalls on 2026-10-01. A…

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

22 comments0 positive reactions50 days openEvidence score 67/100Project Radar 96
bugarea: deliveryconfirmed
#8
Product Capability workflows · CodingREPEATED ACROSS 13 PROJECTS

[FEAT] oMo native support

Observed in 777genius/agent-teams-ai · TypeScript · AGPL-3.0

What the reporter described: Summary Support the harness oMo native Problem oMo native is a new harness evolve from the plugin of opencode, agent-teams-ai currently have no support of it. Area Which part of the app would this affect? Provider runtime (Claude, Codex, OpenCode) Describe the solution you'd like Support oMo native Describe…

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

4 comments1 positive reactions52 days openEvidence score 59/100Project Radar 90

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.