AI Agent Radar
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.

56 signals · Last data refresh Sep 25, 2026, 8:54 PM UTC

ISSUE SCAN COVERAGE36 / 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.
6 Product Capability signals
#1
Provider interoperability · CodingREPEATED ACROSS 8 PROJECTS

Make Gemini less of a sycophant

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

What the reporter described: What would you like to be added? I need gemini-cli to be less of a sycophant and more like a trusted equal. For example, I am working on designing and architecting complex software. Every response from gemini is prefaced with this sycophantic mirroring language: You are having the exact realization that every great…

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

27 comments39 positive reactions432 days openEvidence score 95/100Project Radar 97
priority/p2area/agentStalestatus/bot-triaged
Start guided sprint →Original GitHub Issue ↗Project analysis →
#2
Provider interoperability · CodingREPEATED ACROSS 8 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 8 independent repositories. This is stronger than one backlog item, but still requires direct user validation.

127 comments110 positive reactions218 days openEvidence score 90/100Project Radar 97
priority/p1area/enterprisekind/customer-issue🔒 maintainer only
Start guided sprint →Original GitHub Issue ↗Project analysis →
#3
Tool execution & lifecycle · CodingREPEATED ACROSS 2 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 2 independent repositories. This is stronger than one backlog item, but still requires direct user validation.

18 comments2 positive reactions251 days openEvidence score 71/100Project Radar 96
Start guided sprint →Original GitHub Issue ↗Project analysis →
#4
Runtime & deployment environments · CodingREPEATED ACROSS 2 PROJECTS

[FEAT] Run web ui on dedicated cloud

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

What the reporter described: Is your feature request related to a problem? Please describe. Are is possible run this software on server without electron? Describe the solution you'd like Hosted web ui to manage agents accessible by configured port for manage agents from remote machines.

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

3 comments0 positive reactions126 days openEvidence score 56/100Project Radar 91
enhancement
Start guided sprint →Original GitHub Issue ↗Project analysis →
#5
Product Capability workflows · CodingREPEATED ACROSS 8 PROJECTS

I'm planning a new PR to solve a big problem with agent communication

Observed in 23blocks-OS/ai-maestro · TypeScript · MIT

What the reporter described: I'm planning a new PR to solve a big problem with agent communication. Maybe you didn't used the communication between agents much, but I'm troubled by the complete lack of restrictions on the message exchange inside ai-maestro. THE PROBLEM My problem presented when I started using the agent on multiple projects. I…

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

10 comments0 positive reactions217 days openEvidence score 54/100Project Radar 82
Start guided sprint →Original GitHub Issue ↗Project analysis →
#6
Product Capability workflows · CodingREPEATED ACROSS 8 PROJECTS

feat(fortemi): certify Fortemi Server as the first-class scale-out backend

Observed in jmagly/aiwg · TypeScript · MIT

What the reporter described: Parent: #160 Depends on: #166 Related: #163, #164, #1664, #1684, #1686, #1687, #1689 Summary Make Fortemi Server the primary documented scale-out option after SQLite. This issue covers the live shared/server-backed path, not only the Fortemi Core static JSON cache. AIWG currently has three Fortemi planes that must…

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

4 comments0 positive reactions32 days openEvidence score 52/100Project Radar 82
enhancementP1-highconstructionblocked
Start guided sprint →Original GitHub Issue ↗Project analysis →

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.