[FEATURE] Surface stale open PRs that Claude Code opened on the user's behalf

Summary

PRs opened by Claude Code (or by the user, from a Claude Code session) can sit open and untouched indefinitely with nothing tracking them once the originating session ends. Please add a way to surface "PRs you opened via Claude Code that are still open, with no recent activity" so they don't get silently forgotten.

Current behavior

Reviewing my own GitHub history against my Claude Code session history: several PRs opened during Claude Code sessions remain open weeks later, with no later session ever referencing them again — e.g. multiple PRs on one of my active repos, and PRs opened during a specific short-lived integration effort on another repo. There's no built-in signal anywhere in Claude Code (sidebar, notifications, session list) that these are still pending; the only way to notice is to separately check GitHub directly, which defeats the point of using an assistant that already knows it opened them.

Motivation

Claude Code already tracks a lot of session-to-repo context (which session touched which repo, when). PRs it opens are a natural extension of that same graph, but currently they vanish from view the moment the session that created them ends or gets archived. For someone running many concurrent projects, "did that PR from three weeks ago ever get merged?" is a real, recurring question with no good answer inside the tool that created the PR in the first place.

Proposed behavior

1. Track PR provenance. When Claude Code opens a PR (via gh pr create or equivalent), record the link between the session and the PR URL.
2. Periodic staleness check. Surface PRs above some age threshold (e.g. 14 days) that are still open and have had no new commits/comments — as a distinct, dismissible list, not a blocking interruption.
3. One entry point to review them all — e.g. a "Pending PRs" section in the sidebar or a digest-style summary (could combine with the Routines digest in #79080, or stand alone).
4. Dismissible/snoozable per-PR, since some PRs are intentionally left open (e.g. awaiting external review) and don't need repeated nagging.

Why it matters

• Closes a real gap between "Claude opened this on your behalf" and "you actually know its current state" — right now that link is severed the moment the session ends.
• Reduces the quiet accumulation of forgotten work-in-progress across many repos, which is easy to lose track of at scale (I have PRs open on repos I haven't opened a Claude Code session against in weeks).

Related issues (adjacent, not duplicates)

• #79080 [FEATURE] Consolidated digest for multiple scheduled Routines firing close together — same "digest/rollup" shape, different subject (PRs vs Routine runs); could plausibly share UI if both are built.
• #6235 Feature Request: Support AGENTS.md — unrelated mechanism, but same general theme of Claude Code retaining more durable cross-session state about a repo.

Notes

• Reviewed for duplicates before filing (searched "stale open pull request reminder follow-up") — nothing found describing this specific ask as of 2026-07-19.
• Staleness threshold and snooze/dismiss behavior should be configurable so this doesn't become noisy for workflows that intentionally keep PRs open for a while (e.g. long review cycles).