We've been using issue-graph to answer: what should we work on next? It prioritizes work using signals like engagement and time open, surfaces patterns across the backlog and gives software factories a better way to coordinate agent work GitHub today, more providers soon
Introducing issue-graph Find related work before you start ▲ Existing fixes and open follow-ups ▲ Superseded PRs and backlog items to verify ▲ PR review state and conflicts by author ▲ Works with your coding agent

Sep 24, 2026 · 7:41 PM UTC

12
13
222
28,571
Sort replies: Relevant Recent Liked
Replying to @ctatedev
the related-issue dump is the useful bit. agents keep reopening stuff that’s already fixed two tickets over. if this stops that loop i’d actually run it before starting a session.
1
1
204
Replying to @ctatedev
Any plans to support Linear?
1
1
78
Replying to @ctatedev
engagement points the wrong way for an agent factory: the most-discussed items are usually the ones needing the most human judgment, so ranking by it queues agent hours behind review slots. rank by 'can this run end to end unattended' and throughput stops being human-gated.
40
Replying to @ctatedev
This feels like an important layer for multi-agent development. Before assigning work, understanding related issues, existing fixes and conflicting PRs can matter as much as the coding task itself.
137
Replying to @ctatedev
This is where AI coding gets really interesting: the bottleneck shifts from “what should we build?” to “what should we build next?” Turning the backlog into a continuously ranked set of opportunities could be a huge unlock for agent-driven teams.
2
Replying to @ctatedev
vercel never disappoints 🙌🏻
2
171
Replying to @ctatedev
So cool
2
154
Replying to @ctatedev
that's insane
1
40