Find related work
before you start

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
Read-only access to GitHub and Linear.
vercel-labs/portless80 captured · 16 clusters
Open issues and pull requests in vercel-labs/portless grouped into 5 root-cause clusters#540 · PR · fix(proxy): keep one proxy per state directory#521 · Issue · proxy start -p starts an untracked second proxy and overwrites proxy.pid, so proxy stop kills the wrong one#541 · PR · fix(cli): give concurrent runs different app ports#533 · Issue · Concurrent starts can get the same app port; a child that survives EADDRINUSE leaves its route pointing at another app#460 · PR · feat(ports): add appPortStrategy and appPortRange for stable or sequential app ports#459 · Issue · Proposal: appPortStrategy and appPortRange, so an app's port can be stable or sequential instead of random#415 · Issue · Feature Request: Look Up a Route’s Port#318 · Issue · Redirect direct localhost:<port> access to the registered portless URL#436 · Issue · App startup retries proxy on occupied Portless port and times out#556 · PR · fix(cli): drive dispatch and help from one command list#557 · PR · fix(cli): parse command flags in one place and exit 2 on usage errors#558 · PR · fix(cli): keep stdout for results and add --json to list, get, and doctor#559 · PR · fix(cli): confirm clean, report its failures, and only prune what portless owns#560 · PR · docs(cli): shorten the main help and keep proxy options under proxy --help#520 · PR · fix(cli): reject unknown alias and proxy stop flags#369 · Issue · A partial hosts write leaves a block portless cannot remove, and clean reports success#536 · PR · fix(clean): remove the unprivileged marker with the other proxy state files#527 · PR · fix(trust): skip the prompt when the CA is already trusted#526 · Issue · `portless trust` asks for authorization again when the CA is already trusted#470 · PR · fix(bun): prepare TLS contexts for registered app hostnames#469 · Issue · HTTPS under Bun: nested hosts get the *.localhost cert because Bun ignores SNICallback#418 · Issue · TLS SNI accepts arbitrary hostnames and performs unbounded certificate generation#412 · PR · fix: trust Linux Chrome certificates in the user NSS database#336 · Issue · NixOS: portless trust fails with update-ca-certificates ENOENT#407 · PR · feat(cli): add `--no-worktree` to `portless run` to match `portless get`#326 · Issue · Add --no-worktree support when running apps with explicit names#372 · Issue · feat: support configurable worktree label placement for multi-service hostnames#398 · PR · feat: let the worktree prefix be set explicitly (--prefix / PORTLESS_PREFIX)#340 · PR · feat: add worktree hostname template config#377 · PR · feat: Add flat worktree hostnames#432 · PR · fix: allow Tailscale hosts in Vite#310 · Issue · Vite host allowlist does not include Tailscale `.ts.net` host when using `PORTLESS_TAILSCALE=1`#425 · PR · feat: add `--tailscale-http` for `tailnet`s without MagicDNS#335 · PR · Support for custom Ngrok URLs#347 · Issue · localtunnel support as an alternative to grok#390 · Issue · Add --datum sharing backend● Proxy/app port allocation 9● CLI dispatch/flags/clean 8● TLS/CA trust 7● Worktree hostnames 6● Tunnels & sharing 6
5 of the 16 root-cause clusters an agent proposed for vercel-labs/portless, captured 2026-11-07.

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.

closesmentionscross-ref#412#430#418#455
  • Closing keywords and linked pull requests
  • Mentions and cross-references
  • Review state, draft status, and overlapping files
Terminal
issue-graph open vercel-labs/portless
Map a repository

Linear

Issues in a workspace or a whole project, with read-only browser sign-in.

blocksparent ofrelatedENG-21ENG-34ENG-27ENG-40
  • Blocking, related, and duplicate relations in both directions
  • Parents and sub-issues
  • Native workflow states and attachment links
Terminal
issue-graph linear ENG-123 --workspace your-workspace --open
Connect Linear

Your tracker

Any other tracker, exported to the normalized dashboard model.

relationrelationrelationitemitemitemitem
  • Items, native states, and typed relationships in one JSON file
  • The same filters, Heat ranking, and exact view links
  • No provider requests or credentials at query time
Terminal
issue-graph query --input model.json --open
Import a model

Group open work by root cause

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.

  1. Proxy/app port allocation

    9

    Proxy instances and app ports are not coordinated, causing duplicate proxies, port collisions and unstable ports

  2. CLI dispatch/flags/clean

    8

    CLI parsing, help, output streams and clean logic are scattered and inconsistent

  3. TLS/CA trust

    7

    Certificate issuance and CA trust handling are wrong across platforms and runtimes

  4. Worktree hostnames

    6

    Worktree prefix and placement in hostnames is not configurable

Terminal
issue-graph cluster vercel-labs/portless
issue-graph cluster vercel-labs/portless --apply answer.json

Rank what to fix first

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.

  1. 5#541 fix(cli): give concurrent runs different app ports16.1
  2. 7#533 Concurrent starts can get the same app port; a child that survives EADDRINUSE leaves its route pointing at another app14.2
  3. 6#558 fix(cli): keep stdout for results and add --json to list, get, and doctor15
  4. 2#559 fix(cli): confirm clean, report its failures, and only prune what portless owns20
  5. 3#470 fix(bun): prepare TLS contexts for registered app hostnames16.9
  6. 1#326 Add --no-worktree support when running apps with explicit names30
  7. 4#372 feat: support configurable worktree label placement for multi-service hostnames16.4
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 --budget 80 --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

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.

Read the agent workflow
Collect

The CLI reads GitHub and Linear references and reports missing data.

Inspect

Your agent filters saved captures, ranks open work, and returns the exact dashboard view.

Decide

Review the suggested actions and check the code before closing issues or merging PRs.

Map your backlog before the next fix

Requires Node.js 20 or later. Sign in with the GitHub CLI or connect Linear.

Terminal
npm install -g issue-graph@latest
Get started