Map related issues and pull requests across GitHub and Linear, group open work by root cause, and open the exact view in your browser.
$
npm install -g issue-graph@latest
npm install -g issue-graph@latest
Read-only access to GitHub and Linear.
vercel-labs/portless80 captured · 16 clusters
5 of the 16 root-cause clusters an agent proposed for vercel-labs/portless, captured 2026-11-07.IssuePR
Bring every tracker into one graph
Each provider follows the references its tracker records and keeps native states. GitHub and Linear are built in, and other trackers can import the same normalized model. Saved runs open in one dashboard with a project switcher.
GitHub
Issues and pull requests in a repository, through your GitHub CLI login.
The dashboard starts with connected components. To group by underlying defect instead, ask your agent: issue-graph cluster prints the task, and cluster --apply loads its answer for you to review. These are 4 of the 16 clusters an agent proposed in one run on vercel-labs/portless.
Proxy/app port allocation
9
Proxy instances and app ports are not coordinated, causing duplicate proxies, port collisions and unstable ports
Heat measures discussion, not severity. It weighs comments, participants, reactions, inbound references, and age. Change a weight to reorder the list, then keep the weights you prefer with issue-graph config set.
#540 fix(proxy): keep one proxy per state directory11.2
#521 proxy start -p starts an untracked second proxy and overwrites proxy.pid, so proxy stop kills the wrong one4.4
5#541 fix(cli): give concurrent runs different app ports16.1
7#533 Concurrent starts can get the same app port; a child that survives EADDRINUSE leaves its route pointing at another app14.2
#460 feat(ports): add appPortStrategy and appPortRange for stable or sequential app ports14.1
#459 Proposal: appPortStrategy and appPortRange, so an app's port can be stable or sequential instead of random7.1
#415 Feature Request: Look Up a Route’s Port9
#318 Redirect direct localhost:<port> access to the registered portless URL13.4
#436 App startup retries proxy on occupied Portless port and times out3.3
#556 fix(cli): drive dispatch and help from one command list9
#557 fix(cli): parse command flags in one place and exit 2 on usage errors11
6#558 fix(cli): keep stdout for results and add --json to list, get, and doctor15
2#559 fix(cli): confirm clean, report its failures, and only prune what portless owns20
#560 docs(cli): shorten the main help and keep proxy options under proxy --help14
#520 fix(cli): reject unknown alias and proxy stop flags8.4
#369 A partial hosts write leaves a block portless cannot remove, and clean reports success12.5
#536 fix(clean): remove the unprivileged marker with the other proxy state files5.2
#527 fix(trust): skip the prompt when the CA is already trusted7.3
#526 `portless trust` asks for authorization again when the CA is already trusted4.3
3#470 fix(bun): prepare TLS contexts for registered app hostnames16.9
#469 HTTPS under Bun: nested hosts get the *.localhost cert because Bun ignores SNICallback9.9
#310 Vite host allowlist does not include Tailscale `.ts.net` host when using `PORTLESS_TAILSCALE=1`11.6
#425 feat: add `--tailscale-http` for `tailnet`s without MagicDNS8.7
#335 Support for custom Ngrok URLs9.6
#347 localtunnel support as an alternative to grok6.1
#390 Add --datum sharing backend4.6
Open items from the vercel-labs/portless clusters above, scored in your browser with the CLI's Heat formula. Bar colors match their clusters.
Capture, filter, and open the exact view
Capture once, filter the saved run from the CLI, and open the same result in the dashboard. Structured output keeps your agent and your browser on the same work.
80 open items captured within an explicit budget
issue-graph
$ issue-graph open vercel-labs/portless--budget80--format json --no-open
vercel-labs/portless
Open items captured: 80References not crawled: 40
Saved locally. Collection stopped at the 80-item budget.
Next: ask your agent to group related work
issue-graph cluster vercel-labs/portless
$ issue-graph query github:vercel-labs/portless--state open --kind Issue --heat-top25--view rank --json--no-open
Captured: 80Matched: 10
Open issues · Heat ≥ 8.3
vercel-labs/portless#313OPENCloudflare tunnel support
Heat 33.2
vercel-labs/portless#326OPENAdd --no-worktree support when running apps with explicit names
Heat 26.6
First two results. Heat measures discussion, not severity.
$ issue-graph query github:vercel-labs/portless--state open --kind Issue --heat-top25--view rank --json--open
{ "opened": true}
Use issue-graph with your coding agent
Install the skill to let your agent inspect related work, propose clusters, and return a filtered dashboard link before making changes.