Observed arrival · 2026-09-20
issue-graph maps the work around a GitHub issue
A read-only CLI traces related issues, competing pull requests, and unresolved follow-ups before maintainers or coding agents start work.
- For
- GitHub maintainers and coding agents
- Worth noticing
- The core graph is deterministic and read-only; an optional agent task can cluster the references.
Field notes
The tool begins with an issue or pull request and follows references across repositories, exposing typed relationships, status, and coverage. Its example starts from vercel-labs/portless issue 427 and surfaces four related items, including merged and open pull requests. The page separates deterministic evidence gathering from optional agent-assisted clustering, and presents JSON output for tools alongside readable terminal output for people.
Observed signals
Read the marks
Editorial observations of this landing page, not a rating.
One card from the complete issue